| To: | "'XFS Mailing List'" <linux-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Oops removing files on a full f/s |
| From: | Christopher McCrory <chrismcc@xxxxxxxxxxxxxxxx> |
| Date: | Mon, 18 Jun 2001 19:54:26 -0700 |
| Organization: | PriceGrabber.com |
| References: | <200106190149.f5J1nLo32245@jen.americas.sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux 2.4.5-0.2.9smp i686; en-US; rv:0.9.1+) Gecko/20010606 |
Hello... I just kind of picked a message from this thread at random to reply to. I just filled up a xfs filesystem to 100%, then deleted the large files I was copying in. No oops using updated sgi rpm kernel [chrismcc@dev chrismcc]$ cat /proc/version Linux version 2.4.5-0.2.9_SGI_XFS_20010613 (root@exclaim) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Thu Jun 14 00:51:24 CDT 2001 Steve Lord wrote: Yes, a backtrace from this would be really useful, also, in the backtrace<snip> <snip>fsstress filled up /usr 100% so I was going remove the p* directories and files. This provoked an oops: -- Juha -- Christopher McCrory "The guy that keeps the servers running" chrismcc@xxxxxxxxxxxxxxxx http://www.pricegrabber.com I don't make jokes in base 13. Anyone who does should get help. --Douglas Adams |
| Previous by Date: | RE: Oops removing files on a full f/s, Juha Saarinen |
|---|---|
| Next by Date: | 3ware and AMI raids, ron mckelvey |
| Previous by Thread: | RE: Oops removing files on a full f/s, Juha Saarinen |
| Next by Thread: | Re: Oops removing files on a full f/s, Christopher McCrory |
| Indexes: | [Date] [Thread] [Top] [All Lists] |