From: David Vidal Rodriguez <vidalrod@informatik.tu-muenchen.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: [reiserfs-list] Reiserfs fragments my MP3
Date: Tue, 12 Jun 2001 14:06:03 +0200 [thread overview]
Message-ID: <3B2605AB.703A7F67@in.tum.de> (raw)
In-Reply-To: 20010611154917.F7798@vestdata.no
>
> BTW: It isn't clear from your previous mail that this in fact a
> filesystem problem. The output from fsck may or may not confirm that it
Though this is a big off-topic, I have compiled the 2.4.5 kernel with reiser
within it, but I moved back immediatedly to 2.4.4 after I saw that
unmounting a Reiserfs LV causes an oops -- and a kernel hang when trying to
unmount further Reiserfs LVs... ouch... not strange that there might be data
corruption with this kernel version!
--
------------------------------------------------------------------------
David Vidal R. (vidalrod <at> in DOT tum DOT de)
next prev parent reply other threads:[~2001-06-12 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010610222138.A21955@mind.bartosch.net>
2001-06-10 20:27 ` [linux-lvm] Re: [reiserfs-list] Reiserfs fragments my MP3 Peter Bartosch
2001-06-11 4:44 ` Peter Bartosch
2001-06-11 13:49 ` Ragnar Kjørstad
2001-06-12 12:06 ` David Vidal Rodriguez [this message]
2020-11-27 16:17 ` Holger Grothe
2001-06-12 15:43 ` Werner John
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=3B2605AB.703A7F67@in.tum.de \
--to=vidalrod@informatik.tu-muenchen.de \
--cc=linux-lvm@sistina.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;
as well as URLs for NNTP newsgroup(s).