| To: | Seth Mos <knuffie@xxxxxxxxx> |
|---|---|
| Subject: | Re: [OOPS] XFS in large Maildir |
| From: | Daniel Stone <daniel@xxxxxxxxx> |
| Date: | Sun, 24 Jun 2001 20:52:53 +1000 |
| Cc: | Daniel Stone <daniel@xxxxxxxxx>, linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <Pine.BSI.4.10.10106241216500.12216-100000@xxxxxxxxxxxxx> |
| Mail-followup-to: | Seth Mos <knuffie@xxxxxxxxx>, Daniel Stone <daniel@xxxxxxxxx>, linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| Organisation: | Sadly lacking |
| References: | <Pine.BSI.4.10.10106241216500.12216-100000@xxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.18i |
On Sun, Jun 24, 2001 at 12:18:00PM +0200, Seth Mos wrote: > On Sun, 24 Jun 2001, Daniel Stone wrote: > > > Hi guys, > > I've attached the ksymoops output from Linux 2.4.6-pre3-xfs (CVS tree from > > some point). I'll try an update now, but when I try to access stuff in > > ~/Maildir/netfilter/cur (~7k files in it), XFS just OOPSes. The OOPS I > > attached was from mutt, but it also successfully hangs ls, so I doubt it's a > > mutt bug. > > Have you tried running xfs_repair -n on the filesystem to see if something > is wrong? Was the kernel compiled with 2.96-?? of 2.91.66? I haven't tried anything on the filesystem yet, and it was compiled with Debian (sid aka unstable)'s 2.95.3 snapshot. -- 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: XFS on recent -ac kernels, Seth Mos |
|---|---|
| Next by Date: | Re: [OOPS] XFS in large Maildir, Seth Mos |
| Previous by Thread: | Re: [OOPS] XFS in large Maildir, Seth Mos |
| Next by Thread: | Re: [OOPS] XFS in large Maildir, Seth Mos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |