From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs locks
Date: Sun, 7 Mar 2004 22:27:25 -0500 [thread overview]
Message-ID: <b0fb761c6a2655ac4a242e71faffc440@plan9.bell-labs.com> (raw)
In-Reply-To: <200403072020.i27KKcAN081068@adat.davidashen.net>
On Sun Mar 7 15:22:37 EST 2004, dvd@davidashen.net wrote:
> > in a previous message, with various debugging prints turned on
> > and inserted, there seemed to be driver requests to abort a command.
>
> write is being aborted, because it is asked to write at offset
> not present on the disk. It looks like the in-memory structure
> is corrupt.
>
> > you don't seem to see the problem unless you power cycle,
> > and although i don't use it as much as i did, i still use kfs a
> > fair bit (and i do sometimes just switch off that machine),
> > and i don't see similar problems.
> > now, it's quite likely that i'm running an older version of kfs,
>
> It is quite likely that your machine is slower. If I slow down
> the kfs or kernel code by inserting more debugging, the problem
> disappears because the structure is flushed before being overwritten.
>
> > actual cause of wrenwrite errors before trying to guess what and
> > where the problem might be!
>
> offsets are negative vlongs.
The offset is supposed to be checked way before getting to the
ATA driver:
1) the write and seek system calls check the offset is not negative;
2) the higher level of the disc driver checks the address requested
is within the partition.
What does your partition table look like?
next prev parent reply other threads:[~2004-03-08 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 17:55 David Tolpin
2004-03-07 19:56 ` Charles Forsyth
2004-03-07 20:03 ` David Tolpin
2004-03-07 20:12 ` Charles Forsyth
2004-03-07 20:20 ` David Tolpin
2004-03-08 3:27 ` jmk [this message]
2004-03-08 5:26 ` David Tolpin
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=b0fb761c6a2655ac4a242e71faffc440@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).