All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: Bill Davidsen <davidsen@tmr.com>
Cc: 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: Fri, 3 Feb 2006 07:57:29 +0200	[thread overview]
Message-ID: <200602030757.29640.vda@ilport.com.ua> (raw)
In-Reply-To: <43E25E39.4010908@tmr.com>

On Thursday 02 February 2006 21:32, Bill Davidsen wrote:
> >>reiserfstune -s 1024 /dev/xxxx
> > 
> > I had reiserfsprogs 3.6.11 and reiserfstune (above command) made my /dev/sdc3
> > unmountable without -t reiserfs. I upgraded reiserfsprogs to 3.6.19 and now
> > reiserfsck /dev/sdc3 reports no problems, but mount problem persists:
> > 
> > # mount -t reiserfs /dev/sdc3 /.3
> > # umount /.3
> > # mount /dev/sdc3 /.3
> > mount: you must specify the filesystem type
> > # dmesg | tail -3
> > br: port 1(ifi) entering forwarding state
> > FAT: bogus number of reserved sectors
> > VFS: Can't find a valid FAT filesystem on dev sdc3.
> > 
> > "chown -Rc <n>:<m> ." now does not OOM kill the box, so this issue
> > is resolved, thanks!
> > 
> > Can I restore sdc3 somehow that I won't need -t reiserfs in mount command?
> > You can find result of
> > 
> > dd if=/dev/sdc3 of=1m bs=1M count=1
> > 
> > at http://195.66.192.167/linux/1m
> 
> At the risk of stating the obvious:
> 1 - is reaser a module, and is it loaded?
> 2 - did this ever work? I think you said you removed the entry from 
> fstab, was the filetype there which made it work?

1 - not a module, 2 - fstab line was "/dev/sdc3 /.3 auto noatime,rw 1 1".
But anyway. mount problem is solved now, mount from util-linux 2.11p
tried to "autodetect" fs and thought it's a FAT partition.

mount from busybox 1.0 works.
--
vda

      reply	other threads:[~2006-02-03  5:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28 14:13 Recursive chmod/chown OOM kills box with 32MB RAM 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
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 [this message]

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=200602030757.29640.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=Reiserfs-Dev@namesys.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.