From: "Nathaniel W. Turner" <nate@houseofnate.net>
To: Marc Lehmann <schmorp@schmorp.de>
Cc: xfs@oss.sgi.com
Subject: Re: crashes with xfs_fsr in 2.6.25-2-amd64 and 2.6.26-1-amd64 (debian) (f'up)
Date: Wed, 29 Apr 2009 13:29:23 -0400 [thread overview]
Message-ID: <49F88E73.7060403@houseofnate.net> (raw)
In-Reply-To: <20090428032406.GA14234@schmorp.de>
Hi Marc,
Marc Lehmann wrote:
> It also happens to the same filesystem each time (maybe because
> it does the heavy I/O),a and it is also the same filesystem where
> xfs_repair hangs in an endless loop often (but not always). (see
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525880)
>
> The filesystem was created a month or so ago using blocksize of 512 and
> lazy-count=1, but I have many of those xfs filesystems.
>
> Since this is a production system and I have no backup abilities, I have
> to no choice but to reformat the disk now.
>
I'm not sure about the root cause of your crash, but I just wanted to
mention that before you blow away this filesystem, you should probably
try repairing it with a recent version of xfs_repair (like 3.0.0).
ftp://oss.sgi.com/projects/xfs/cmd_tars/
Also, I have seen similar problems to those described in Debian bug
525880 with xfs_repair not making progress (although I'm running
32-bit), and adding "-P" to the xfs_repair invocation helped in many cases.
Cheers,
nate
--
Nathaniel W. Turner
http://houseofnate.net/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-29 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 3:24 crashes with xfs_fsr in 2.6.25-2-amd64 and 2.6.26-1-amd64 (debian) (f'up) Marc Lehmann
2009-04-29 17:29 ` Nathaniel W. Turner [this message]
2009-04-29 17:58 ` Russell Cattelan
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=49F88E73.7060403@houseofnate.net \
--to=nate@houseofnate.net \
--cc=schmorp@schmorp.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox