mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guest section DW <dwguest@win.tue.nl>
To: Doug Siebert <dsiebert@divms.uiowa.edu>, linux-kernel@vger.kernel.org
Subject: Re: Issues with disk block devices
Date: Tue, 13 Mar 2001 14:18:28 +0100	[thread overview]
Message-ID: <20010313141828.A6599@win.tue.nl> (raw)
In-Reply-To: <200103130836.CAA06967@server.divms.uiowa.edu>
In-Reply-To: <200103130836.CAA06967@server.divms.uiowa.edu>; from Doug Siebert on Tue, Mar 13, 2001 at 02:36:09AM -0600

On Tue, Mar 13, 2001 at 02:36:09AM -0600, Doug Siebert wrote:

> This note is sort of a half question half bug report.

[devices are accessed in blocksize-size units, and this unit is changed
upon a mount, and is 1024 to start with; this gives problems if one
wants to access the last few sectors of a drive]

Yes, a known problem.
It will go in 2.5.
The problem is old, but until recently nobody complained -
sacrificing 1 or 3 sectors at the end of a disk to the roundoff
was something like sacrificing 62 sectors to DOS-compatibility.
These days people put partition tables and other interesting stuff
at the very end of a disk and this suddenly becomes a problem.

If you really want to touch the last sector of a disk, then
you can start a partition an integral number of blocks before
the end. Messy, but at least all of the disk is accessible.
An ioctl to change the block size of a partition (or the full disk)
is slightly better, but is dangerous - it can be used only
when nothing is mounted, etc.
(My memory is bad, but it seems to me that such an ioctl was
proposed, and I suggested to add the checks [not in use,
no mount, not swap device] but I don't know what happened
to this proposal afterwards. Must check.)

Andries


      reply	other threads:[~2001-03-13 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-13  8:36 Doug Siebert
2001-03-13 13:18 ` Guest section DW [this message]

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=20010313141828.A6599@win.tue.nl \
    --to=dwguest@win.tue.nl \
    --cc=dsiebert@divms.uiowa.edu \
    --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

all inboxes | Powered by JetHome®