From: Eric Sandeen <sandeen@sandeen.net>
To: "Martín Marqués" <martin.marques@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS errors... can't repair them
Date: Mon, 21 Feb 2011 12:02:21 -0600 [thread overview]
Message-ID: <4D62A8AD.1060202@sandeen.net> (raw)
In-Reply-To: <AANLkTik-ds_7kb62KTtrmuKewt1QN-JU1yfZhurx+sTj@mail.gmail.com>
On 2/21/11 9:30 AM, Martín Marqués wrote:
> I have a system with /home in XFS format. Just today I tried to copy a
> big file, not knowing that there was little space left in the device.
>
> The thing is that when the FS got filled up, the system didn't let me
> access /home anymore (not even as root). I rebooted and tried to use
> xfs_check and xfs_repair, with no luck (it looks as if they do
> nothing).
Showing us the output would help....
Use xfs_repair, not xfs_check. If you want check-only, use xfs_repair -n.
> The other FS on the same disk work OK. Just /home is giving me
> problems. This is not on a RAID or a LVM.
>
> BTW, no reboot /home doesn't get mounted printing a lot of error messages:
>
> Feb 21 10:57:02 dagobah kernel: XFS mounting filesystem sda3
> Feb 21 10:57:02 dagobah kernel: Starting XFS recovery on filesystem:
> sda3 (logdev: internal)
> Feb 21 10:57:04 dagobah kernel: XFS internal error
> XFS_WANT_CORRUPTED_GOTO at line 1652 of file fs/xfs/xfs_alloc.c.
> Caller 0xffffffffa0fc1e6c
Looks like a corrupted or at least unreplayable log. Did the box lose
power prior to this?
Repair won't replay a dirty log, and the only way to clear the log is to
mount it. If mounting fails, you may have to use xfs_repair -L to
zero out the log, then do the repair.
> Feb 21 10:57:04 dagobah kernel: Pid: 1618, comm: mount Tainted: P
> 2.6.34.7-66.fc13.x86_64 #1
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-21 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 15:30 XFS errors... can't repair them Martín Marqués
2011-02-21 16:46 ` Martín Marqués
2011-02-21 18:02 ` Eric Sandeen [this message]
2011-02-21 22:56 ` Martín Marqués
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=4D62A8AD.1060202@sandeen.net \
--to=sandeen@sandeen.net \
--cc=martin.marques@gmail.com \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.