Re: ФС на сторадж
Ed пишет:
>> Именно это и делает xfs, не?
> afaik нет.
Пришли к выводу, что это не так начиная с ядра 2.6.22.
Если я правильно понял английский текст:
http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_see_binary_NULLS_in_some_files_after_recovery_when_I_unplugged_the_power.3F
Q: Why do I see binary NULLS in some files after recovery when I
unplugged the power?
Update: This issue has been addressed with a CVS fix on the 29th March
2007 and merged into mainline on 8th May 2007 for 2.6.22-rc1.
XFS journals metadata updates, not data updates. After a crash you are
supposed to get a consistent filesystem which looks like the state
sometime shortly before the crash, NOT what the in memory image looked
like the instant before the crash.
Since XFS does not write data out immediately unless you tell it to with
fsync, an O_SYNC or O_DIRECT open (the same is true of other
filesystems), you are looking at an inode which was flushed out, but
whose data was not. Typically you'll find that the inode is not taking
any space since all it has is a size but no extents allocated (try
examining the file with the xfs_bmap(8) command).
--
Dmitri Samsonov
Reply to: