On Fri, Oct 28 2011 at 10:30am -0400,
Antonio Trande <anto.trande(a)gmail.com> wrote:
I don't know if useful but during boot with kernel 3.0 appears:
$ dmesg | grep multipath
> [ 4.113786] device-mapper: multipath: version 1.3.0 loaded
> [ 4.164462] device-mapper: multipath round-robin: version 1.0.0 loaded
> [ 35.443230] multipathd[1184]: /lib/udev/scsi_id exitted with 1
> [ 35.443682] multipathd[1184]: /lib/udev/scsi_id exitted with 1
Must i consider this problem as a kernel 3.1 bug ?
I don't know where come from this multipath configuration, i have always
done simple Fedora installations.
You said that you saw the problem with Linux 3.0 too though? But only
if fsck is enabled.. yet btrfs doesn't yet have a publicly available
fsck... so you need to clarify your 3.0 comment earlier.
That aside, I'd imagine that anaconda unnecessarily introduced a
multipath layer for your storage when you really don't have multiple
paths. What does 'multipath -ll' show?
2011/10/27 Antonio Trande <anto.trande(a)gmail.com>
> >do you have multipath configured on your box?
> If i have understand the 'multipath concept', yes. fdisk
output<http://www.fpaste.org/KXvm/>
>
>
> >How often can you reproduce this problem.
> Only with Kernel 3.1.
> If fsck is enabled on / partition (btrfs filesystem) also with Kernel 3.0