From: Jordan <ledzep37@home.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5
Date: Thu, 31 May 2001 17:04:50 -0500 [thread overview]
Message-ID: <3B16C002.E615CB80@home.com> (raw)
In-Reply-To: <E155a3W-00084H-00@the-village.bc.nu>
Alan Cox wrote:
>
> > I'm staying on 2.4.5-ac5 for whatever it's worth (putting my life on the
> > line for the community? kidding...) and will report anything new. I will
> > be on the lookout for later ac patches, 2.4.6 ... and hopefully anything
> > anybody can share with me about this. I hope we'll see an end to these
>
> Can you tell me if 2.4.5-ac4 is ok. ac5 has a small 'obviously correct'
> reiserfs module unload change that seems the first suspect
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I have seen this same problem with unmounting in 2.4.5-ac5, it was
perfectly fine in 2.4.5-ac3 and ac4. I would guess the module unload is
what did it.
Jordan
next prev parent reply other threads:[~2001-05-31 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B167AFD.EC1897E1@namesys.com>
2001-05-31 18:23 ` unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5 bug) Federico Sevilla III
2001-05-31 21:32 ` unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5 Alan Cox
2001-05-31 22:04 ` Jordan [this message]
2001-06-01 8:56 ` thunder7
2001-06-01 9:37 ` Lech Szychowski
2001-06-01 13:48 ` Lech Szychowski
2001-06-01 17:10 ` Hans Reiser
2001-06-01 17:47 ` unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: Alan Cox
2001-06-01 18:05 ` unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5 Alexander Viro
2001-06-02 6:13 ` Hans Reiser
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=3B16C002.E615CB80@home.com \
--to=ledzep37@home.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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