| To: | Daniel Stone <daniel@xxxxxxxxx> |
|---|---|
| Subject: | Re: [OOPS] XFS in large Maildir |
| From: | Daniel Stone <daniel@xxxxxxxxx> |
| Date: | Sun, 24 Jun 2001 22:19:19 +1000 |
| Cc: | Seth Mos <knuffie@xxxxxxxxx>, linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <20010624213151.A27190@kabuki.sfarc.net> |
| Mail-followup-to: | Daniel Stone <daniel@xxxxxxxxx>, Seth Mos <knuffie@xxxxxxxxx>, linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| Organisation: | Sadly lacking |
| References: | <Pine.BSI.4.10.10106241255490.12216-100000@xs4.xs4all.nl> <20010624213151.A27190@kabuki.sfarc.net> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.18i |
> > if you can run xfs_repair -n to see if it produces error output. > > xfs_repair -n works on a mounted filesystem but does not change anything. > > > > If you do see errors you need to unmount the fs and run xfs_repair and see > > if you can reproduce the oops after that there must be other issues. > > > > Can you also apt-get 2.95.4? I believe that one currently is in unstable. > > Even if it is just to test for compiler differences. xfs_repair saw nothing, and it works just fine with -pre5-xfs. :) d -- Daniel Stone <daniel@xxxxxxxxx> <Nuke> "can NE1 help me aim nuclear weaponz????? /MSG ME!!" |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Access control lists, Jan-Frode Myklebust |
|---|---|
| Next by Date: | Re: [OOPS] XFS in large Maildir, Seth Mos |
| Previous by Thread: | Re: [OOPS] XFS in large Maildir, Daniel Stone |
| Next by Thread: | Re: [OOPS] XFS in large Maildir, Seth Mos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |