From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michael Cree <mcree@orcon.net.nz>
Cc: linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
warns@pre-sense.de
Subject: Re: Alpha no longer recognises certain partition tables (v2.6.38)
Date: Wed, 16 Mar 2011 08:03:42 -0700 [thread overview]
Message-ID: <AANLkTinvRJNZGrKT0pbFBcHoe2LOeSVMd2CEBaKdbU2u@mail.gmail.com> (raw)
In-Reply-To: <4D80695D.8080903@orcon.net.nz>
On Wed, Mar 16, 2011 at 12:40 AM, Michael Cree <mcree@orcon.net.nz> wrote:
>
> OK, I've fallen for that and created too many partitions on my system disk.
> When using your patch dmesg reports:
>
> [ 7.511714] sd 1:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50
> TB/1.36 TiB)
> [ 7.551753] sd 1:0:0:0: [sdb] Write Protect is off
> [ 7.572261] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> [ 7.591792] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
> doesn't support DPO or FUA
> [ 7.633785] OSF: 10 partitions
> [ 7.654292] sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8
> [ 7.675777] sd 1:0:0:0: [sdb] Attached SCSI disk
Ok, no problem.
I'll increase the value of OSF_MAX_PARTITIONS to 18 (which is what
fits in a 512 byte sector), and mark it for back-porting into stable
too.
Thanks for testing.
> I could get it back to eight partitions but it will require copying the
> largest partition to another disk and back again as that partition does not
> meet the conditions for resizing.
Oh, no need for that. There really isn't any real technical limit for
the "limit to 8 partitions", and we don't cause regressions.
Linus
next prev parent reply other threads:[~2011-03-16 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 9:06 Michael Cree
2011-03-15 15:10 ` Linus Torvalds
2011-03-15 16:17 ` Linus Torvalds
2011-03-16 7:40 ` Michael Cree
2011-03-16 15:03 ` Linus Torvalds [this message]
2011-03-16 1:23 ` Michael Cree
2011-03-16 4:09 ` Dialup Jon Norstog
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=AANLkTinvRJNZGrKT0pbFBcHoe2LOeSVMd2CEBaKdbU2u@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
--cc=warns@pre-sense.de \
/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®