From: Denis Vlasenko <vda@ilport.com.ua>
To: Edward Shishkin <edward@namesys.com>
Cc: Chris Mason <mason@suse.com>, Hans Reiser <reiser@namesys.com>,
linux-kernel@vger.kernel.org,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: Recursive chmod/chown OOM kills box with 32MB RAM
Date: Wed, 1 Feb 2006 16:57:55 +0200 [thread overview]
Message-ID: <200602011657.55761.vda@ilport.com.ua> (raw)
In-Reply-To: <200602011626.17697.vda@ilport.com.ua>
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
next prev parent reply other threads:[~2006-02-01 14:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 14:13 Denis Vlasenko
2006-01-28 15:01 ` Denis Vlasenko
2006-01-28 16:11 ` Denis Vlasenko
2006-01-30 6:11 ` Hans Reiser
2006-01-30 12:28 ` Denis Vlasenko
2006-02-01 15:21 ` Bernd Eckenfels
2006-02-03 6:21 ` Denis Vlasenko
2006-01-30 13:22 ` Chris Mason
2006-01-21 23:20 ` Pavel Machek
2006-02-02 15:17 ` Denis Vlasenko
2006-02-02 19:34 ` Bill Davidsen
2006-02-01 7:32 ` Denis Vlasenko
2006-02-01 7:42 ` Hans Reiser
2006-02-02 19:26 ` Bill Davidsen
2006-02-01 7:42 ` Denis Vlasenko
2006-02-01 10:15 ` Denis Vlasenko
2006-02-01 11:45 ` Vitaly Fertman
2006-02-01 14:25 ` Denis Vlasenko
2006-02-01 14:59 ` Denis Vlasenko
2006-02-01 11:52 ` Edward Shishkin
2006-02-01 14:26 ` Denis Vlasenko
2006-02-01 14:57 ` Denis Vlasenko [this message]
2006-02-01 15:14 ` Bernd Eckenfels
2006-02-01 15:28 ` Denis Vlasenko
2006-02-02 7:25 ` Denis Vlasenko
2006-02-02 9:42 ` Vitaly Fertman
2006-02-02 11:52 ` Denis Vlasenko
2006-02-02 19:32 ` Bill Davidsen
2006-02-03 5:57 ` Denis Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602011657.55761.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=Reiserfs-Dev@namesys.com \
--cc=edward@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiser@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome