From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [SOLVED] problems while mounting /boot partition
Date: Wed, 08 Aug 2007 14:18:16 -0400 [thread overview]
Message-ID: <1186597096.6259.22.camel@pc.ilinx> (raw)
In-Reply-To: <46B9EF1D.4010907@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
On Wed, 2007-08-08 at 18:28 +0200, Michal Piotrowski wrote:
> Hi Brian,
Hi Michal,
> Brian J. Murrell pisze:
> > I am using Ubuntu Gutsy, which is the in-development branch heading for
> > their next stable release.
>
> You forgot about message subject, so no one has read this report.
Indeed. Very unfortunate. I did re-post with a subject but I have not
seen it show up yet, which I have been waiting for to post the solution.
Maybe I will just do that here and again if it shows up with the subject
posted.
The crux of the problem is that the real partitions are being
mapped/managed by device mapper, which is being used by LVM:
$ ls -l /dev/mapper/
total 0
crw-rw---- 1 root root 10, 63 2007-08-08 04:56 control
lrwxrwxrwx 1 root root 7 2007-08-08 04:56 hda1 -> ../dm-0
lrwxrwxrwx 1 root root 7 2007-08-08 04:56 hda2 -> ../dm-1
lrwxrwxrwx 1 root root 7 2007-08-08 04:56 hda3 -> ../dm-2
This is of course causing those partitions to be opened exclusively,
preventing any further uses (i.e. sys_mount()) from being able to use
them. Only hda3 of those above is actually an LVM PV. hda1 is an ext3
filesystem (/boot) and hda2 is a FAT32 (could even be FAT16) filesystem.
Of course, mounting /dev/dm-0 instead of /dev/hda1 solves the problem.
Why this started with Ubuntu's 2.6.22 kernel in Gutsy, I'm not sure.
Whether it's a new DM feature or some change in the way Ubuntu handles
devices, I don't know. Whatever the case, they need to fix
their /dev/disk/by-uuid mappings anyway:
$ ls -l /dev/disk/by-uuid/ | grep hda
lrwxrwxrwx 1 root root 10 2007-08-08 08:56 12b8250a-d031-4ee1-b486-5e67478d06b4 -> ../../hda1
Cheers,
b.
--
A day in the yard with my son is just like a day at work. He goes
hunting around for stuff and brings it back to me and says: "Hey Dad,
look what I found. The money is for me and the screw is for you."
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-08 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1186504459.6949.40.camel@pc.ilinx>
2007-08-08 16:28 ` problems while mounting /boot partition Michal Piotrowski
[not found] ` <46B9EF1D.4010907@googlemail.com>
2007-08-08 18:18 ` Brian J. Murrell [this message]
2007-08-09 23:57 ` Jan Engelhardt
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=1186597096.6259.22.camel@pc.ilinx \
--to=brian@interlinx.bc.ca \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).