Marco d'Itri wrote:
> On Aug 20, Vincent Danjean <[EMAIL PROTECTED]> wrote:
>
>> I'm not sure at all if this is the correct global solution. But comments
> *Totally wrong*, or I would have already done it.
Probably, but with it I can boot my system.
> Please wait, because I want to rename the udev rules files first.
I think I will keep my fix until you provide the real one.
I love to have my /home when I boot my laptop...
However, I would be VERY pleased if you can give me more information
(or tell me where I can find the information) to know :
- why does my solution not work [1] ?
- does my solution work in my case (no mdadm, only lvm2 with no snapshot)
or can my change trigger big problems for me ?
- how can we debug udev stuff ? (I tried my 'correction' with udevtest
before applying it with udevtrigger but I'm not confortable at all with
this)
Best regards,
Vincent
[1] : now I know my solution does not work everywhere. I try it on another
computer with LVM2 on RAID (mdadm)
'udevtest /block/md-0' try to run something like
'/lib/udev/scsi_id -g -x -n -s /block/dm-0 -d /dev/dm-0'
On my laptop (where LVM2 is installed on real partitions), I get the
information about my ATA disk
On my other computer (where LVM2 is installed on RAID partitions), I get no
information (and no disk/by-*/* is created in this case)
So, it seems that the current rules need that the filesystem is installed
on a disk which can be found with /lib/udev/scsi_id so that symlinks by-*/*
are created for this filesystem.
And it seems that, by chance, with LVM on one disk, something is returned
by /lib/udev/scsi_id. And not for LVM on RAID.
So, now I'm persuaded that my fix is not correct. However :
1) I still do not know if I risk something on my laptop with this setup
2) I do not know why udev need to know a disk to create symlinks for a
filesystem
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
