[EMAIL PROTECTED] wrote:
>I presume you've done "xfs_repair -n" on the partition. This will not do >anything but will tell you if it finds anything wrong. You have to do this >while your erring filesystem is unmounted. If you've done that, any error >messages? Yep. The repair, however, can't proceed since there's no more disk space available, as I've invoked xfs_repair while the system is unmounted before I posted. I don't have the problem as of the present (after mkfs-ing to a fresh start), so I need to deliberately mess with it again to reproduce it. >In light of positivism, reproduce the problem. The easier it is to >reproduce it, the more help you can probably get. Then get on the XFS >mailing list and report whatever you can report. Good stuff to say are: >how to reproduce the problem, what xfs_repair says on a problematic >filesystem, et al. I think it is a race condition that causes this (doing simultaneous file operations such as mass deletion or simultaneous opening of multiple files across v/c's and X terminals was one thing I was doing before the FS f*cked up) when using XFS over large partitions with large files stored in a folder. I'll reproduce the problem once I figure it out (previous problem like that happened around 2 months ago). It's not also because of quota because the previous time this mess happened I'm not yet implementing quota on my XFS /home partition. >The XFS developers may ask for your help by asking you to run xfs_db or >something like that to isolate the problem. I should've runned it before proceeding to mkfs. Then I would've been of any help debugging and isolating the problem to its root. Thanks. Paolo Alexis Falcone __________________________________ www.edsamail.com _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
