[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87tye1ckhr.fsf@linux.vnet.ibm.com>
Date: Thu, 14 Apr 2011 13:50:16 +0530
From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To: Dave Jones <davej@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Eric Sandeen <sandeen@...hat.com>
Subject: Re: Linux 2.6.39-rc3
On Tue, 12 Apr 2011 15:21:03 -0400, Dave Jones <davej@...hat.com> wrote:
> On Tue, Apr 12, 2011 at 03:09:34PM -0400, Dave Jones wrote:
>
> > however, the output of mount looks very confused..
> >
> > .38:
> > /dev/mapper/vg_adamo-lv_home on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered)
> >
> > .39:
> > - on /home type 79a9-4526-888c-1f86d35a6704 (rw,relatime,ext4)
> >
> > It looks like /proc/self/mountinfo broke abi.
> >
> > .38:
> > 48 45 253:3 / /home rw,relatime - ext4 /dev/mapper/vg_adamo-lv_home rw,seclabel,barrier=1,data=ordered
> >
> > .39:
> > 46 22 253:3 / /home rw,relatime uuid:f3971858-79a9-4526-888c-1f86d35a6704 - ext4 /dev/mapper/vg_adamo-lv_home rw,seclabel,user_xattr,barrier=1,data=ordered
>
> looks like this was caused by 93f1c20bc8cdb757be50566eff88d65c3b26881f
>
> perhaps adding that string to the end of the line would preserve what mount expects ?
uuid:<value> is the option field as per
Documentation/filesystem/proc.txt. There was an error in libmount
parsing which got fixed upstream recently
you can find the details here
http://thread.gmane.org/gmane.linux.kernel/1121533/focus=52474
-aneesh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists