| To: | Nathan Scott <nathans@xxxxxxx> |
|---|---|
| Subject: | Re: XFS 1.2Pre and nfs problem |
| From: | Žeref Tufan Žen <tufan@xxxxxxxxxx> |
| Date: | Thu, 17 Oct 2002 10:13:37 +0300 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20021017073316.A302869@wobbly.melbourne.sgi.com> |
| Organization: | ITU-CC |
| References: | <20021011124432.253ca55a.tufan@itu.edu.tr> <1034352726.1162.7.camel@rose.americas.sgi.com> <20021012140349.3c28bcc9.tufan@itu.edu.tr> <20021016115430.724d3b18.tufan@itu.edu.tr> <1034779623.15573.0.camel@stout.americas.sgi.com> <20021017073316.A302869@wobbly.melbourne.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Hi,,, On Thu, 17 Oct 2002 07:33:16 +1000 Nathan Scott <nathans@xxxxxxx> wrote: > 990 (EFSCORRUPTED) can be generated by xfs_repair itself (via > libxfs). Its not supposed to happen, but it can. :( Running > ltrace on xfs_repair would help to find the offending routine > in libxfs. I will do it when this evening.. I will post he results... -- Şeref Tufan Şen İTÜ-BİDB Sistem Destek Grubu |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Bug 181] fsx produces file system corruption (fwd), Mike Gigante |
|---|---|
| Next by Date: | Re: Is there something special I need to do?, Andi Kleen |
| Previous by Thread: | Re: XFS 1.2Pre and nfs problem, Nathan Scott |
| Next by Thread: | [2.4.18-14SGI_XFS_1.2a1] xfs_inotobp/xfs_force_shutdown, Axel Thimm |
| Indexes: | [Date] [Thread] [Top] [All Lists] |