From: Andries.Brouwer@cwi.nl
To: michael_e_brown@dell.com
Cc: Matt_Domsch@exchange.dell.com, linux-kernel@vger.kernel.org
Subject: Re: block ioctl to read/write last sector
Date: Wed, 14 Feb 2001 16:43:59 +0100 (MET) [thread overview]
Message-ID: <UTC200102141543.QAA79054.aeb@vlet.cwi.nl> (raw)
> My patch has nothing to do with partitioning.
Yes, you already said that, and I understand you very well.
My suggestion, and I have not checked the code to make sure,
but off-hand it seems to me that it should work,
is to use a partition.
> Disk with 1001 blocks. Hardware 512-byte sector size.
> The block layer uses 1024-byte soft blocksize.
> This means that, at the _end_ of the disk there is a single sector
> that represents half of a software sector.
Maybe. I think that you'll find that these blocks are
relative to the start of the partition, not relative
to the start of the disk.
So if you add a 1-block partition that contains the last
sector of the disk, all should be fine.
Andries
next reply other threads:[~2001-02-14 15:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 15:43 Andries.Brouwer [this message]
2001-02-14 15:56 ` block ioctl to read/write last sector Michael E Brown
2001-02-14 15:59 ` Michael E Brown
-- strict thread matches above, loose matches on Subject: below --
2001-02-14 13:26 Matt_Domsch
2001-02-14 12:31 David Balazic
2001-02-14 14:10 ` Michael E Brown
2001-02-17 7:29 ` Andre Hedrick
2001-02-14 1:00 Matt_Domsch
2001-02-13 23:49 Andries.Brouwer
2001-02-14 14:19 ` Michael E Brown
2001-02-13 22:54 Andries.Brouwer
2001-02-13 19:24 ` Martin K. Petersen
2001-02-14 5:51 ` Michael E Brown
2001-02-14 14:23 ` Martin K. Petersen
2001-02-13 23:37 ` Michael E Brown
2001-02-14 0:21 ` Manfred Spraul
2001-02-14 5:47 ` Michael E Brown
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=UTC200102141543.QAA79054.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=Matt_Domsch@exchange.dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael_e_brown@dell.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.