-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ciro Iriarte wrote: > 2007/10/26, Jeff Mahoney <[EMAIL PROTECTED]>: > Ciro Iriarte wrote: >>>> 2007/10/24, Jeff Mahoney <[EMAIL PROTECTED]>: >>>>> Ok, I just subscribed to this list, so this is the first message I have >>>>> in my inbox on this topic. I've read the rest on the archive. I do >>>>> regularly read opensuse-kernel, though. >>>>> >>>>> First to start with the questions from the bottom up: >>>>> >>>>> ReiserFS doesn't reserve space for anything other than the journal. >>>>> >>>>> ReiserFS doesn't have inodes. It has items that are referenced by keys. >>>>> The only thing there is a "shortage" of is objectids, which are regular >>>>> 32-bit integers. Unless you've managed to create ~ 4 billion files, >>>>> you're not running out of them. >>>>> >>>>> This bug is likely caused by a patch I put into 10.3 that started using >>>>> the first_zero_hint value that is calculated in the bitmap code. The >>>>> calculations have been there for ages, but they haven't been used until >>>>> the 10.3 kernel. It short circuits the bitmap scanning code to skip >>>>> ranges it knows are already used. After the 10.3 release, I decided this >>>>> was a dubious optimization and was likely responsible for problems just >>>>> like this one (bug 331814). I pushed a patch to mainline that rips the >>>>> first_zero_hint code out entirely. >>>>> >>>>> To test this hypothesis, please download and test a kernel from: >>>>> ftp://ftp.suse.com/pub/people/jeffm/suse/testpkgs/331814 >>>>> >>>>> I'm very much interested in feedback to ensure that this solves the > problem. >>>>> Thanks. >>>>> >>>>> - -Jeff >>>>> >>>>> - -- >>>>> Jeff Mahoney >>>>> SUSE Labs >>>> Installed the test kernel but all my reiserfs are read only now... >>>> >>>> FS: >>>> ---------------------------------------------- >>>> mainwks:~> df -h >>>> S.ficheros Tamaño Usado Disp Uso% Montado en >>>> /dev/mapper/system-root >>>> 6,0G 1004M 4,7G 18% / >>>> udev 1007M 120K 1007M 1% /dev >>>> /dev/md0 99M 27M 68M 28% /boot >>>> /dev/mapper/system-datos >>>> 151G 151G 755M 100% /datos >>>> /dev/mapper/system-home >>>> 32G 24G 8,1G 75% /home >>>> /dev/mapper/system-ftp >>>> 15G 15G 306M 99% /srv/ftp >>>> /dev/mapper/system-usr >>>> 5,0G 3,3G 1,4G 71% /usr >>>> /dev/mapper/system-var >>>> 2,0G 417M 1,5G 22% /var >>>> /dev/mapper/system-vmware >>>> 20G 19G 1,8G 92% /var/lib/vmware >>>> ---------------------------------------------- >>>> >>>> Mounted as follow: >>>> >>>> ---------------------------- >>>> mainwks:~> mount >>>> /dev/mapper/system-root on / type ext3 (rw,acl,user_xattr) >>>> proc on /proc type proc (rw) >>>> sysfs on /sys type sysfs (rw) >>>> debugfs on /sys/kernel/debug type debugfs (rw) >>>> udev on /dev type tmpfs (rw) >>>> devpts on /dev/pts type devpts (rw,mode=0620,gid=5) >>>> /dev/md0 on /boot type ext3 (rw,acl,user_xattr) >>>> /dev/mapper/system-datos on /datos type reiserfs (rw) >>>> /dev/mapper/system-home on /home type reiserfs (rw) >>>> /dev/mapper/system-ftp on /srv/ftp type reiserfs (rw) >>>> /dev/mapper/system-usr on /usr type ext3 (rw,acl,user_xattr) >>>> /dev/mapper/system-var on /var type ext3 (rw,acl,user_xattr) >>>> /dev/mapper/system-vmware on /var/lib/vmware type reiserfs (rw) >>>> nfsd on /proc/fs/nfsd type nfsd (rw) >>>> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) >>>> ----------------------- >>>> >>>> Read only messages: >>>> >>>> --------------------- >>>> [EMAIL PROTECTED]:~> echo "dosaokdsa" > hbla >>>> bash: hbla: Sistema de ficheros de sólo lectura >>>> --------------------- >>>> >>>> No space left messages: >>>> >>>> --------------------- >>>> [EMAIL PROTECTED]:~> echo sdad > /datos/peliculas/test >>>> bash: echo: write error: No queda espacio en el dispositivo >>>> >>>> [EMAIL PROTECTED]:~> echo "dosaokdsa" > /srv/ftp/update/10.3/sadad >>>> bash: echo: write error: No queda espacio en el dispositivo >>>> --------------------- > Can you send me the output from dmesg? The file system must have aborted > for some reason.
Ok, I think I really have it this time. That RPM had an old version of the patch that is in the HEAD kernel. It was missing a memset 0 -> 0xff change that would cause the problems you're describing. I'm building an update RPM now, and it'll be posted shortly. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHJgUhLPWxlyuTD7IRAg8KAJsHMudvBUZ5Qy38K64N5Bs184MeWwCgj7yR 4nagiovRHJpxNGexxzs7pjE= =K82I -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
