From: Chris Mason <mason@suse.com>
To: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Cc: Daniel Christiansen <christiansen@albion.edu>,
Oleg Drokin <green@namesys.com>,
reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Error Code 255 and "Permission Denied"
Date: 06 May 2002 21:53:42 -0400 [thread overview]
Message-ID: <1020736422.988.74.camel@tiny> (raw)
In-Reply-To: <3CD725AC.6000708@mb.tu-ilmenau.de>
On Mon, 2002-05-06 at 20:54, Manuel Krause wrote:
> On 05/06/2002 09:12 PM, Daniel Christiansen wrote:
>
> > Everything seems to work by using the 3.x.1b version of reisfsck with
> > --rebuild-tree. Thank you very much, Oleg, for taking the time to solve
> > my problem.
> >
> > I don't know anything about the "write cache enabled" issue below. Is
> > this something I have to change with a jumper, a bios setting, or a
> > software configuration?
> >
Most new IDE drives have this on by default. You can turn it off with
hdparm -W 0, which will make you more able to withstand power failures.
>
> Or is it somekind of connected to Chris Masons thread "2.4.19-pre7 /
> corruption on unwanted reboot"??? If Chris and Jens found bugs on IDE
> interaction with ReiserFS they should really put out a patch soon... ;-)
>
> Chris M.? Is that related eventually? Just a doubt!
I haven't been able to reproduce problems after a crash with pre7, but
Dirk is not often wrong when we reports about a bug. If anyone can
reliably reproduce I'd be grateful.
-chris
next prev parent reply other threads:[~2002-05-07 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 19:12 Error Code 255 and "Permission Denied" Daniel Christiansen
2002-05-07 0:54 ` Manuel Krause
2002-05-07 1:53 ` Chris Mason [this message]
2002-05-07 5:12 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2002-05-06 16:07 Daniel Christiansen
2002-05-06 18:06 ` Oleg Drokin
2002-05-05 16:18 Daniel Christiansen
2002-05-06 11:21 ` Oleg Drokin
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=1020736422.988.74.camel@tiny \
--to=mason@suse.com \
--cc=christiansen@albion.edu \
--cc=green@namesys.com \
--cc=manuel.krause@mb.tu-ilmenau.de \
--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.