search for: bearstech

...d such), to no avail. Since I'm mostly facing ext3 and ext4 filesystems, I wrote a tool based on libe2fs which replaces the 'find /' part by directly going to the ext data structures. It has been working great for me for several months, and I've published it at https://github.com/bearstech/e2find There's a data safety issue I'm not quite sure. I'm using libe2fs to open read-only blockdevices which are mounted and actively written to. It's obviously unsafe (not from the data-loss p.o.v., but from the coherent-retrieved-data p.o.v.), but I've never encountered a...

Hello list, I have troubles with the daily backup of a modest filesystem which tends to take more that 10 hours. I have ext4 all over the place on ~200 servers and never ran into such a problem. The filesystem capacity is 300 GB (19,6M inodes) with 196 GB (9,3M inodes) used. It's mounted 'defaults,noatime'. It sits on a hardware RAID array thru plain LVM slices. The RAID array is

Hi, all I''ve got problems with tc qdisc ingress. I''m using vanillia kernel 2.6.14.4 patched with http://www.ssi.bg/~ja/routes-2.6.14-12.diff, and iproute2-2.6.14-051107. i am using ingress to limit incoming traffic : (DEV is eth1 / DOWNLINK is 7700) # attach ingress policer: tc qdisc add dev $DEV handle ffff: ingress # filter *everything* to it (0.0.0.0/0), drop everything

Hello, I just noticed that 'tune2fs -l' did not returned a "lively" updated information regarding the free inodes count (looks like it's always correct after unmounting). It became suprising after an online resizing operation, where the total inode count was immediatly updated (grown in my case) but the free inode count was the same: one could deduce that suddenly a lot of