From: Eric Sandeen <sandeen@sandeen.net>
To: Mike Gao <ygao.linux@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Question about XFS recovery and error
Date: Fri, 20 Aug 2010 18:13:57 -0500 [thread overview]
Message-ID: <4C6F0C35.3030007@sandeen.net> (raw)
In-Reply-To: <AANLkTi=prcC7ky3ikNTJ+py8XnALGf4THSOCUwqYhxaq@mail.gmail.com>
Mike Gao wrote:
> The USB key is mounted automatically at boot and no error report with
> XFS recovery.
> But when I did a file copy on a USB key which XFS filesystem could be
> corrupted by some reason,
> I got endless repeat of ERROR message printed on the screen.
>
> Should XFS recovery this at the beginning when mounting?
>
> [42949387.250000] Starting XFS recovery on filesystem: sda (logdev:
> internal)
> [42949387.330000] Ending XFS recovery on filesystem: sda (logdev: internal)
> [42949388.600000] Starting XFS recovery on filesystem: sdb1 (logdev:
> internal)
> [42949388.640000] Ending XFS recovery on filesystem: sdb1 (logdev: internal)
>
first off, the above is an indication that you're not cleanly unmounting
the filesystem.
> cp /mnt/USB0disk1/iCarly-4.ts ./iCarly-4-10.ts
>
> [ 3234.740000] Filesystem "sda": XFS internal error
> xfs_btree_check_sblock at line 120 of file fs/xfs/xfs_btree.c. Caller
> 0x8718e102
> [ 3234.740000]
> [ 3234.750000] regs can't be NULL.
> [ 3234.760000] Filesystem "sda": page discard on page 876a1914, inode
> 0x91, offset 91160576.
> [ 3235.150000] Filesystem "sda": XFS internal error
> xfs_btree_check_sblock at line 120 of file fs/xfs/xfs_btree.c. Caller
> 0x8718e102
This is probably a result of a write cache which isn't properly flushed
during use prior to unplug (i.e. barriers; no idea what usb keys have
for write caches etc, but btree errors wouldn't be unheard of due to
lost/reordered writes due to write cache failure)
As to your other question, Michael is right, filesystems don't call out
to userspace repair tools when they encounter an error like this.
You could make xfs_repair run prior to mount, but I'd focus more on
why you're getting a corrupted filesystem in the first place.
-Eric
> Thanks,
> Mike
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-08-20 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 22:32 Question about XFS recovery and error Mike Gao
2010-08-19 23:18 ` Michael Monnerie
2010-08-20 23:13 ` Eric Sandeen [this message]
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=4C6F0C35.3030007@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=ygao.linux@gmail.com \
/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