From: Michael Buesch <mbuesch@freenet.de>
To: Vladimir Saveliev <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Two "maybe" related problems
Date: Wed, 19 May 2004 13:57:27 +0200 [thread overview]
Message-ID: <200405191357.37303.mbuesch@freenet.de> (raw)
In-Reply-To: <1084892983.1431.112.camel@tribesman.namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 18 May 2004 17:09, you wrote:
> This is probably caused by the fact that system oopsed already.
> I would suggest you to boot of rescue system and change /etc/fstab so
> that /dev/hda13 does not get mounted on booting (noauto in fourth field
> of a /etc/fstab's record)
> Do so for other filesystems underlying deveices of which were
> repartitioned.
> reboot in usual way
> if it does not oops on boot (it should not) - mkreiserfs will not get
> stuck
I rebooted and updated reiserfs tools. Now it works as expected.
But should the kernel (reiser4 driver) be "allowed" to oops,
if someone tries to mount a non-existing partition, just because
there's some old and corrupt data left, from a previous filesystem?
Shouldn't it simply refuse to mount?
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAq0uvFGK1OIvVOP4RAn2YAJ9+AYo29gLPT8jZjFdjV7pLka88cACg0vHQ
tvvzO2HGeT/x73FrTbaBJ5I=
=Yg1o
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-05-19 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 14:57 Two "maybe" related problems Michael Buesch
2004-05-18 15:09 ` Vladimir Saveliev
2004-05-19 11:57 ` Michael Buesch [this message]
2004-05-19 12:09 ` Vladimir Saveliev
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=200405191357.37303.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.