All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org, Hans Reiser <reiser@namesys.com>
Subject: Re: ReiserFS buglet
Date: Tue, 24 Sep 2002 12:39:24 +0200	[thread overview]
Message-ID: <20020924103923.GI2442@unthought.net> (raw)
In-Reply-To: <20020924142521.C23185@namesys.com>

On Tue, Sep 24, 2002 at 02:25:21PM +0400, Oleg Drokin wrote:
> Hello!
> 
> On Tue, Sep 24, 2002 at 12:03:38PM +0200, Jakob Oestergaard wrote:
> 
> > It's a question of which errors one wishes to handle, and which you
> > simply choose to ignore.
> 
> Yes, that's true. Reiserfs chose to not handle any HW errors, this is even
> written somewhere in our FAQ.

Fair enough.

...
> Ok, I did.
> You math was wrong, you forgot to account that your number should be divided
> by 128, not 512, since integer itself is 4 bytes long on x86.
> (See message from Itai Nahshon <nahshon@actcom.co.il>, August 7th
> Message-Id: <200208071443.30551.nahshon@actcom.co.il> if you missed that originally.)

Darn !

Thanks for pointing that one out - I missed it.

And you (well nahson@atcom.co.il) is right and I am wrong.

...
> Probably I mssed that part of converstion, then.
> As I see the IDE thing, you tell the hardware that you want to write some amount
> of _sectors_ to the hard drive, and then feed the controller with necessary
> amount of data. If it writes these sectors from the start of the data flow,
> what will it do on data transefer timeout?
> So I still think that data is written on disk in 512 bytes atomic blocks
> until I see IDE device that does otherwise (and then I will probably
> dig some IDE datasheet and find out they are violating some spec ;) )

That would be really interesting.

I mean, my point still stands even though my proof was wrong, unless
someone can come up with a "proof" (a spec would be close enough) that
writes must be 512 bytes.

Thanks,   :)

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2002-09-24 10:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24  7:24 ReiserFS buglet Jakob Oestergaard
2002-09-24  9:21 ` Oleg Drokin
2002-09-24  9:27   ` Jakob Oestergaard
2002-09-24  9:42     ` Hans Reiser
2002-09-24  9:47       ` Jakob Oestergaard
2002-09-24  9:48     ` Oleg Drokin
2002-09-24 10:03       ` Jakob Oestergaard
2002-09-24 10:25         ` Oleg Drokin
2002-09-24 10:39           ` Jakob Oestergaard [this message]
2002-09-24 10:54             ` Oleg Drokin
2002-09-24 11:30           ` Hans Reiser
2002-09-24 11:35             ` 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=20020924103923.GI2442@unthought.net \
    --to=jakob@unthought.net \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@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.