|To:||Steve Lord <lord@xxxxxxx>|
|Subject:||Re: Filesystem Consistency Issues|
|From:||Eric Sandeen <sandeen@xxxxxxx>|
|Date:||Wed, 07 Dec 2005 23:39:58 -0600|
|Cc:||Linux-XFS Mailing List <linux-xfs@xxxxxxxxxxx>|
|References:||<20051204142506.GE2605@xxxxxxxxxxx> <17299.32438.100855.316477@xxxxxxxxxxxxxxxxxx> <20051207200333.GA5279@xxxxxxxxxxxxxx> <439745EB.3050903@xxxxxxx>|
|User-agent:||Mozilla Thunderbird 1.0.6 (Macintosh/20050716)|
Steve Lord wrote:
XFS always does a scan of the log on mount, it always replays the log if it is not terminated with an unmount record. The fact that the filesystem is mounted readonly during startup should have no affect on this. XFS will run recovery on a read only mount.
The only time xfs will not replay the log on mount is if the -block device- itself is readonly; for example a read-only snapshot or... um... maybe a cdrom? :) But Steve is right (of course!) - the "ro" option does not prevent log replay.
On inode unlink, XFS adds inodes to an unlinked inode list until the space in the inode is freed when the last reference count is released. Removing these inodes is part of the recovery process. It sounds like there may be an issuewith this part of recovery.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: XFS Mount Hangs the Partition (on latest kernel + many old 2.6.x ones), Nathan Scott|
|Next by Date:||Re: deep chmod|chown -R begin to start OOMkiller, David Chinner|
|Previous by Thread:||Re: Filesystem Consistency Issues, Steve Lord|
|Next by Thread:||TAKE 946444 - pquota, Nathan Scott|
|Indexes:||[Date] [Thread] [Top] [All Lists]|