On 2013.07.11 at 13:58 +1000, Dave Chinner wrote: > On Thu, Jul 11, 2013 at 05:36:21AM +0200, Markus Trippelsdorf wrote: > > On 2013.07.11 at 10:31 +1000, Dave Chinner wrote: > > > On Wed, Jul 10, 2013 at 11:06:34AM +0200, Markus Trippelsdorf wrote: > > > > While bisecting a system hang, caused by the drm gpu subsystem, my root fs got > > > > corrupted: > > > > > > That's a filesystem that has unlinked inodes on the unlinked list. > > > They get cleaned up during log replay. All the other "errors" are > > > related to cleaning these up.... > > > > > > So what is making you think there is a corruption? What's the error > > > being reported when you are using the filesystem? i.e. what's the > > > entire process you go through before you get to finding this > > > problem? > > > > I was loosing my KDE settings bit by bit with every reboot during the > > bisection. First my window-rules disappeared, then my desktop background > > changed to default, then my taskbar moved from top to the bottom, etc. > > In the end I had to restore all my .files from backup. > > That's not filesystem corruption. That sounds more like someone not > using fsync in the apropriate place when overwriting a file.... Ok. Sorry for using the wrong term. > > And please note that xfs_repair unlinked the inodes _after_ the > > filesystem has been mounted and unmounted normally. > > Which means we might not be processing the unlinked lists correctly > and leaking them. If repair is finding the inodes in the AGI > unlinked lists, then recovery should be finding them, too. Not > processing them and not clearing the AGI bucket tends to imply that > recovery failed to read the AGI buffer. > > What error messages are in dmesg, if any? And what kernel are you > running? There are no error messages in dmesg. I'm running the latest Linus tree. -- Markus _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
