mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: Szakacsits Szabolcs <szaka@sienet.hu>
Cc: Andries Brouwer <aebr@win.tue.nl>,
	fledely <fledely@bgumail.bgu.ac.il>,
	linux-ntfs-dev@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: Accessing odd last partition sector (was: [Linux-NTFS-Dev] mkntfs dirty volume marking)
Date: Sat, 10 Apr 2004 22:13:01 +0100	[thread overview]
Message-ID: <20040410211301.GW31500@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0404102301400.840-100000@mlf.linux.rulez.org>

On Sat, Apr 10, 2004 at 11:04:45PM +0200, Szakacsits Szabolcs wrote:
> 
> On Sat, 10 Apr 2004 viro@parcelfarce.linux.theplanet.co.uk wrote:
> > On Sat, Apr 10, 2004 at 10:29:37PM +0200, Andries Brouwer wrote:
> > > On Fri, Apr 09, 2004 at 01:38:51PM +0200, Szakacsits Szabolcs wrote:
> > > 
> > > > > TODO.ntfsprogs conatins the following TODO item under mkntfs:
> > > > >  - We don't know what the real last sector is, thus we mark the volume
> > > > > dirty and the subsequent chkdsk (which will happen on reboot into
> > > > > Windows automatically) recreates the backup boot sector if the Linux
> > > > > kernel lied to us about the number of sectors.
> > > 
> > > The ioctl BLKGETSIZE64 will tell you the size (in bytes) of a block device.
> > 
> > So will lseek() to SEEK_END, actually (both 2.4 and 2.6).
> > And yes, last sector _is_ accessible for dd(1) et.al.
> 
> In 2.6? Not for 2.4 when I tried (it wasn't the latest 2.4 kernel).

2.4 logics around block size handling is broken; we probably could backport
that series of patches, though.  2.6 simply sets block size to GCD(page size,
device size), so we don't have to worry about all that crap.

  reply	other threads:[~2004-04-10 21:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001601c41db7$aa0a02e0$0100000a@p667>
2004-04-09 11:38 ` Szakacsits Szabolcs
2004-04-10 20:29   ` Andries Brouwer
2004-04-10 20:54     ` viro
2004-04-10 21:04       ` Szakacsits Szabolcs
2004-04-10 21:13         ` viro [this message]
2004-04-10 22:23           ` Szakacsits Szabolcs
2004-04-10 22:55             ` viro
2004-04-10 23:14               ` Szakacsits Szabolcs
2004-04-16 13:26           ` Szakacsits Szabolcs

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=20040410211301.GW31500@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=aebr@win.tue.nl \
    --cc=fledely@bgumail.bgu.ac.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=szaka@sienet.hu \
    /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®