From: Eric Sandeen <sandeen@sandeen.net>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com, xfs@pzystorm.de
Subject: Re: Problem with XFS on USB 2TB HD
Date: Sun, 19 Dec 2010 11:30:39 -0600 [thread overview]
Message-ID: <4D0E413F.50204@sandeen.net> (raw)
In-Reply-To: <20101219155703.0dba96ff@galadriel.home>
On 12/19/10 8:57 AM, Emmanuel Florac wrote:
> Le Sun, 19 Dec 2010 03:04:21 +0100 vous écriviez:
>
>> ERROR: The filesystem has valuable metadata changes in a log which
>> needs to be replayed.
>
> Given this message, you'll have to run xfs_repair with the zero log
> option ( -L ). This is dangerous, but it can't get much worse anyway.
I agree with that approach.
> Run xfs_repair -L /device , you should be able to mount your filesystem
> afterwards, however any data under change at the time of failure will
> most probably be lost.
And something seems to have really whacked your filesystem; odds are
the USB transport was lying to xfs one way or another about completed
writes, and when it went away, things were not consistent on disk
as expected.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-19 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 11:26 Problem with XFS on USB 2TB HD Kevin Richter
2010-12-19 2:04 ` Kevin Richter
2010-12-19 2:37 ` Stan Hoeppner
2010-12-19 14:57 ` Emmanuel Florac
2010-12-19 17:30 ` Eric Sandeen [this message]
2010-12-20 0:10 ` Dave Chinner
2010-12-20 2:56 ` Kevin Richter
2010-12-20 4:51 ` Dave Chinner
2010-12-20 9:55 ` Emmanuel Florac
2011-01-12 23:37 ` Kevin Richter
2011-01-13 13:15 ` Extreme fragmentation when backing up via NFS Phil Karn
2011-01-14 4:51 ` Dave Chinner
2011-01-13 21:52 ` Problem with XFS on USB 2TB HD Geoffrey Wehrman
2010-12-20 8:59 ` Michael Monnerie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0E413F.50204@sandeen.net \
--to=sandeen@sandeen.net \
--cc=eflorac@intellique.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@pzystorm.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox