2.1.63: `ext2_rmdir: d_count=112, pruning'

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Chris Evans: "Re: My desires for 2.2"
• Previous message: Shaw Carruthers: "Is this a problem with klogd( in kernels 2.1.xx)?"

The following operation produces kernel messages mentioned in subject:

vvv:/usr/local/src# tar xfz mc-4.1.8.tar.gz
vvv:/usr/local/src# rm -r mc-4.1.8
ext2_rmdir: d_count=112, pruning
ext2_rmdir: d_count=20, pruning
ext2_rmdir: d_count=10, pruning
ext2_rmdir: d_count=17, pruning
ext2_rmdir: d_count=13, pruning
ext2_rmdir: d_count=24, pruning
ext2_rmdir: d_count=91, pruning
ext2_rmdir: d_count=7, pruning
ext2_rmdir: d_count=2, pruning
ext2_rmdir: d_count=27, pruning
ext2_rmdir: d_count=37, pruning
ext2_rmdir: d_count=3, pruning
ext2_rmdir: d_count=26, pruning
ext2_rmdir: d_count=11, pruning
ext2_rmdir: d_count=4, pruning
ext2_rmdir: d_count=6, pruning
ext2_rmdir: d_count=29, pruning
ext2_rmdir: d_count=34, pruning

I.e., immediately after untarring a big archive, I recursively delete the tree.
This is 100% reproducible.

-- 
With best regards,
                   Vladimir.

• Next message: Chris Evans: "Re: My desires for 2.2"
• Previous message: Shaw Carruthers: "Is this a problem with klogd( in kernels 2.1.xx)?"