这是一个创建于 1166 天前的主题，其中的信息可能已经有所发展或是发生改变。
有同事误删了文件，发现以后已经及时 umount 掉分区了。
使用 extundelete 进行文件恢复时候，扫描 inode2 节点，但是结果是空的
有遇到过这种情况吗？
服务器是 ubuntu 的，分区是通过阵列卡做的 RAID5，extundelete 是 apt 安装的
Inode is Allocated
File mode: 16877
Low 16 bits of Owner Uid: 0
Size in bytes: 4096
Access time: 1634537588
Creation time: 1626155556
Modification time: 1626155556
Deletion Time: 0
Low 16 bits of Group Id: 0
Links count: 5
Blocks count: 8
File flags: 524288
File version (for NFS): 0
File ACL: 0
Directory ACL: 0
Fragment address: 0
Direct blocks: 127754, 4, 0, 0, 1, 6085, 0, 0, 0, 0, 0, 0
Indirect block: 0
Double indirect block: 0
Triple indirect block: 0
File name | Inode number | Deleted status
root@server:~#
使用 extundelete 进行文件恢复时候，扫描 inode2 节点，但是结果是空的
有遇到过这种情况吗？
服务器是 ubuntu 的，分区是通过阵列卡做的 RAID5，extundelete 是 apt 安装的
Inode is Allocated
File mode: 16877
Low 16 bits of Owner Uid: 0
Size in bytes: 4096
Access time: 1634537588
Creation time: 1626155556
Modification time: 1626155556
Deletion Time: 0
Low 16 bits of Group Id: 0
Links count: 5
Blocks count: 8
File flags: 524288
File version (for NFS): 0
File ACL: 0
Directory ACL: 0
Fragment address: 0
Direct blocks: 127754, 4, 0, 0, 1, 6085, 0, 0, 0, 0, 0, 0
Indirect block: 0
Double indirect block: 0
Triple indirect block: 0
File name | Inode number | Deleted status
root@server:~#
Select Language