| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: nfsd: non-standard errno: -990 |
| From: | Ondřej Surý <ondrej@xxxxxxxx> |
| Date: | Mon, 22 Nov 2004 12:48:01 +0100 |
| In-reply-to: | <419E71CC.7010406@sgi.com> |
| References: | <1100776614.4833.22.camel@localhost.localdomain> <419CAC5E.6070806@sgi.com> <1100787175.4833.35.camel@localhost.localdomain> <419D063A.4010809@sgi.com> <1100852618.25135.18.camel@localhost.localdomain> <419DFE30.5050202@sgi.com> <1100874902.13322.7.camel@localhost.localdomain> <419E71CC.7010406@sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Hi Eric, thanks for tip on newer xfs tools. We were able to repair filesystem and it's working ok again. Best regards, Ondrej Sury. On Fri, 2004-11-19 at 16:21 -0600, Eric Sandeen wrote: > OndÅej Surà wrote: > > > Ok, we will try to use 2.6.25 version and I will report result > > afterwards. Is there something you are particulary interested if it > > crashes again more then full log of activity? > > > > I will try to use xfs_repair -n as first step and if it finishes, then > > use it for real. Any other suggestions? > > That sounds good. Also, have you made sure that there are no other > errors in the logs (or dmesg) about general IO problems? 990 errors can > come after the filesystem has shut down due to errors, including > underlying disk problems... -- OndÅej Surà <ondrej@xxxxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | xfs badblocks, Gaspar Bakos |
|---|---|
| Next by Date: | [2.6.10-rc2] XFS filesystem corruption, Jan De Luyck |
| Previous by Thread: | Re: nfsd: non-standard errno: -990, Eric Sandeen |
| Next by Thread: | 2GB filesize limit?, Mike Burger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |