From: Oleg Drokin <green@namesys.com>
To: Hendrik Visage <hvisage@envisage.co.za>
Cc: reiserfs-list@namesys.com
Subject: Re: Crashes with corruption of disk data
Date: Sun, 21 Jul 2002 22:26:35 +0400 [thread overview]
Message-ID: <20020721222635.A22526@namesys.com> (raw)
In-Reply-To: <20020721001030.GM229@hvs.envisage.co.za>
Hello!
This is a know issue.
If you muck with FS data of mounted reiserfs filesystem, not using
reiserfs in-kernel driver, you are asking for trouble.
Bye,
Oleg
On Sun, Jul 21, 2002 at 02:10:30AM +0200, Hendrik Visage wrote:
>
> Hi there,
>
> I've came upon a crash situation (quite repeatable) with reiserfs,
> but NOT with ext2/3.
>
> Using Vanilla 2.4.17 + XFS + EVMS-1.1.0-rc4
>
> (1) using evmsn I created a logical volume, mkfs'd it, and
> mounted it. FS used was ext3 & reiserfs
>
> (2) went into evmsn again & destroyed[b] the volume with a
> unmkfs[a]
>
> (3) forced exited evmsn
>
> (4) tried to access the "still" mounted fs & umount it
>
> At this point, ext2/3 would let go of the mounted FS,
> however, reiserfs consistently crashed into the SGI/XFS
> Kernel debugger :(
>
> I'm of believe that this would be seen as a non check of the
> validity of the underlying diskdata. I believe this test could
> be repeated with a dd if=/dev/zero of=/dev/mounted/reiser but haven't
> yet done so (sleep time), but would be able to report or help with
> finding the errors if it is seen as a bug, as I haven't seen documentation
> to the contrary.
>
> Greetz
> Hendrik
>
> Notes
> [a] because a miss assumption which are being fixed, this was
> wrongly executed, but the "issue" still hold :(
> [b] it weren't actually destroyed, though the unmks were run,
> as the kernel wouldn't let go of a mounted volume, thus the
> forced in (3)
prev parent reply other threads:[~2002-07-21 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 0:10 Crashes with corruption of disk data Hendrik Visage
2002-07-21 18:26 ` Oleg Drokin [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=20020721222635.A22526@namesys.com \
--to=green@namesys.com \
--cc=hvisage@envisage.co.za \
--cc=reiserfs-list@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.