From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, aeb@cwi.nl,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Why aren't partitions limited to fit within the device?
Date: Mon, 16 Oct 2006 11:54:32 +0100 [thread overview]
Message-ID: <1160996072.24237.13.camel@localhost.localdomain> (raw)
In-Reply-To: <1160983735.32674.4.camel@frg-rhel40-em64t-03>
Ar Llu, 2006-10-16 am 09:28 +0200, ysgrifennodd Xavier Bestel:
> > Hmmm.. So Alan things a partially-outside-this-disk partition
> > shouldn't show up at all, and Andries thinks it should.
> > And both give reasonably believable justifications.
>
> Maybe the whole part table should be marked as "weird" to let userspace
> run a diagnostics/repair tool on the disk.
I actually like the "read only" suggestion that was made. Allow data
access but protect from damage.
Both options will allow 'repair' of a broken partition table as the
partition will show up in fdisk which accesses stuff directly, and when
that causes a revalidate it will re-appear to the kernel.
Incidentally the question of exactly what libata should do about HPA
handling also needs sorting out.
Alan
next prev parent reply other threads:[~2006-10-16 10:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 23:50 Why aren't partitions limited to fit within the device? Neil Brown
2006-10-13 1:02 ` Andries Brouwer
2006-10-13 1:31 ` Neil Brown
2006-10-13 15:07 ` Alan Cox
2006-10-13 18:16 ` jdow
2006-10-16 0:08 ` Neil Brown
2006-10-16 1:22 ` Wakko Warner
2006-10-16 1:31 ` Randy Dunlap
2006-10-16 4:09 ` Kyle Moffett
2006-10-16 6:40 ` Andries Brouwer
2006-10-16 6:43 ` dean gaudet
2006-10-16 7:28 ` Xavier Bestel
2006-10-16 10:54 ` Alan Cox [this message]
2006-10-17 6:05 ` Chris Wedgwood
2006-10-15 8:29 ` Ville Herva
2006-10-15 23:50 ` Neil Brown
2006-10-16 5:27 ` Ville Herva
2006-10-16 6:02 ` Andries Brouwer
2006-10-16 6:20 ` Ville Herva
2006-10-16 6:27 ` dean gaudet
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=1160996072.24237.13.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=aeb@cwi.nl \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=xavier.bestel@free.fr \
/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