Messages in this thread | | | From | Denis Vlasenko <> | Subject | Re: Recursive chmod/chown OOM kills box with 32MB RAM | Date | Wed, 1 Feb 2006 16:57:55 +0200 |
| |
On Wednesday 01 February 2006 16:26, Denis Vlasenko wrote: > 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@namesys.com, ** > ** 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 > ###########
I hit [reply] too fast.
reiserfsck 3.6.19 reports success now even without -j option, but still (kernel 2.6.15.1):
# mount /dev/sdc3 /.3 mount: you must specify the filesystem type
How can I fix it? -- vda - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |