Sudden File System Corruption
Mike Dacre
mike.dacre at gmail.com
Fri Dec 6 17:15:33 CST 2013
Hey Guys,
Here is the repair log from right after the corruption happened. The
repair was successful.
-Mike
On Fri, Dec 6, 2013 at 2:56 PM, Ben Myers <bpm at sgi.com> wrote:
> Hey Mike,
>
> On Thu, Dec 05, 2013 at 04:40:46PM -0800, Mike Dacre wrote:
> > On Thu, Dec 5, 2013 at 4:23 PM, Ben Myers <bpm at sgi.com> wrote:
> > > On Thu, Dec 05, 2013 at 04:06:27PM -0800, Mike Dacre wrote:
> > > > I sent you the output of the xfs_repair command, and also the
> logprint,
> > > but
> > > > I couldn't get a metadump as the filesystem is mounted. I can't
> unmount
> > > > the file system, it is too important. Sorry.
> > > >
> > > > The logprint is in a tar archive at
> > > > ftp://shell.sgi.com/receive/mike_dacre/mike-xfs-files.tar.bz2
> > >
> > > Thanks for the info. Could you clarify a couple things for me so that
> I
> > > know
> > > what I'm looking at?
> > >
> > > 1) How did you create the logprint file? Was the filesystem mounted at
> > > the time?
> > >
> >
> > The filesystem was mounted, I created it with this command: `xfs_logprint
> > -C xfs_logdump.txt /dev/sda1`
>
> Oh, ok. The logprint I'm looking for would have to be taken immediately
> after
> the forced shutdown. Sorry for the confusion.
>
> > > 2) Is the xfs_repair.log you sent the output of the very first run of
> > > xfs_repair? Or, is it the output from a second incident? Was the
> > > filesystem
> > > mounted at the time?
> > >
> >
> > That is from the first run of xfs_repair, after the filesystem corrupted.
> > I ran it with the filesystem unmounted.
>
> It's great that you have this. And an interesting repair log. The good
> news
> is that it doesn't look like the corruption that xfs_repair doesn't fix,
> the
> bad news is that I don't recognise it. If you wouldn't mind posting the
> repair
> log to the list, I think that would help. At least it would get some more
> eyes
> on it.
>
> Thanks much,
> Ben
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20131206/1b23e7d0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xfs_repair.log
Type: text/x-log
Size: 128472 bytes
Desc: not available
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20131206/1b23e7d0/attachment-0001.log>
More information about the xfs
mailing list