Re: Recursive chmod/chown OOM kills box with 32MB RAM

[Denis Vlasenko]

On Wednesday 01 February 2006 13:52, Edward Shishkin wrote:
> ># reiserfstune -s 1024 /dev/sdc3
> >reiserfstune: Journal device has not been specified. Assuming journal is on the main device (/dev/sdc3).
> >
> >Current parameters:
> >
> >Filesystem state: consistent
> >
> >Reiserfs super block in block 16 on 0x823 of format 3.6 with standard journal
> >Count of blocks on the device: 2094474
> >Number of bitmaps: 64
> >Blocksize: 4096
> >Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 1019710
> >Root block: 32941
> >Filesystem is cleanly umounted
> >Tree height: 4
> >Hash function used to sort names: "r5"
> >Objectid map size 54, max 972
> >Journal parameters:
> >        Device [0x0]
> >        Magic [0x2cac04df]
> >        Size 8193 blocks (including 1 for journal header) (first block 18)
> >        Max transaction length 1024 blocks
> >        Max batch size 900 blocks
> >        Max commit age 30
> >Blocks reserved by journal: 0
> >Fs state field: 0x0:
> >sb_version: 2
> >inode generation number: 293892
> >UUID: 7b3aa1ab-40bd-44da-98dc-b37b21f7add0
> >LABEL:
> >Set flags in SB:
> >        ATTRIBUTES CLEAN
> >reiserfstune: Current journal parameters:
> >        Device [0x0]
> >        Magic [0x2cac04df]
> >        Size 8193 blocks (including 1 for journal header) (first block 18)
> >        Max transaction length 1024 blocks
> >        Max batch size 900 blocks
> >        Max commit age 30
> >WARNING: wrong transaction max size (1024). Changed to 511
> >reiserfstune: New journal parameters:
> >        Device [0x0]
> >        Magic [0x70dbc903]
> >        Size 1024 blocks (including 1 for journal header) (first block 18)
> >        Max transaction length 511 blocks
> >        Max batch size 449 blocks
> >        Max commit age 30
> >Reiserfs super block in block 16 on 0x823 of format 3.6 with non-standard journal
> >Count of blocks on the device: 2094474
> >Number of bitmaps: 64
> >Blocksize: 4096
> >Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 1019710
> >Root block: 32941
> >Filesystem is cleanly umounted
> >Tree height: 4
> >Hash function used to sort names: "r5"
> >Objectid map size 54, max 972
> >Journal parameters:
> >        Device [0x0]
> >        Magic [0x70dbc903]
> >        Size 1024 blocks (including 1 for journal header) (first block 18)
> >        Max transaction length 511 blocks
> >        Max batch size 449 blocks
> >        Max commit age 30
> >Blocks reserved by journal: 8193
> >Fs state field: 0x0:
> >sb_version: 2
> >inode generation number: 293892
> >UUID: 7b3aa1ab-40bd-44da-98dc-b37b21f7add0
> >LABEL:
> >Set flags in SB:
> >        ATTRIBUTES CLEAN
> >reiserfstune: ATTENTION: YOU ARE ABOUT TO SETUP THE NEW JOURNAL FOR THE "/dev/sdc3"!
> >AREA OF "/dev/sdc3" DEDICATED FOR JOURNAL WILL BE ZEROED!
> >Continue (y/n):y
> >Initializing journal - 0%....20%....40%....60%....80%....100%
> >Syncing..ok
> >
> ># mount /dev/sdc3 /.3 -o noatime
> >mount: you must specify the filesystem type
> >
> ># dmesg | tail -4
> >br: topology change detected, propagating
> >br: port 1(ifi) entering forwarding state
> >FAT: bogus number of reserved sectors
> >VFS: Can't find a valid FAT filesystem on dev sdc3.
> >
> ># reiserfsck /dev/sdc3
> >reiserfsck 3.6.11 (2003 www.namesys.com)
> >
> >*************************************************************
> >** If you are using the latest reiserfsprogs and  it fails **
> >** please  email bug reports to reiserfs-list@xxxxxxxxxxx, **
> >** providing  as  much  information  as  possible --  your **
> >** hardware,  kernel,  patches,  settings,  all reiserfsck **
> >** messages  (including version),  the reiserfsck logfile, **
> >** check  the  syslog file  for  any  related information. **
> >** If you would like advice on using this program, support **
> >** is available  for $25 at  www.namesys.com/support.html. **
> >*************************************************************
> >
> >Will read-only check consistency of the filesystem on /dev/sdc3
> >Will put log info to 'stdout'
> >
> >Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
> >Failed to open the journal device ((null)).
> >
> >	Wow... 8(
> >--
> >vda
> >  
> >
> 
> would you try
> reiserfsck -j /dev/sdc3 /dev/sdc3

Updated tools to reiserfsprogs-3.6.19, then:

# reiserfsck -j /dev/sdc3 /dev/sdc3
reiserfsck 3.6.19 (2003 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@xxxxxxxxxxx, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/sdc3
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Wed Feb  1 16:24:20 2006
###########
Replaying journal..
No transactions found
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
        Leaves 8075
        Internal nodes 52
        Directories 1792
        Other files 31865
        Data block pointers 1058363 (0 of them are zero)
        Safe links 0
###########
reiserfsck finished at Wed Feb  1 16:26:33 2006
###########

--
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/