Marking as fixed since this is now working in Intrepid.
** Changed in: udev (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: dmraid (Ubuntu)
Status: New = Fix Released
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
I'm having same issue on hardy on two different computers, one 32bit, one
64bit.
I am using ubuntu on a mdraid system, and additionally use part of the dmraid
for ubuntu two.
I can not use UUID because it is not unique.
Output of blkid: (64bit system hardy 2.6.24-19-generic kernel)
/dev/sda1:
Luke:
In current Hardy Beta, my original issue (not being able to mount dmraid
partition using UUID / conflicting outputs from blkid and ls -l on
/dev/disk/by-uuid) seems to be fixed. I can mount the NTFS partition
using UUID in my fstab now.
FYI:
[EMAIL PROTECTED]:~$ sudo blkid
[sudo] password
Kay, I see the above linked patch from the ataraid list is still not in
rc14. I might give it some testing in the next few weeks, but is it
something that we might want? I can see how it would clearly help
distinguish the UUIDs from standard disk UUIDs, in terms of mounting
partitions.
--
UUID's
Has there been any progress on the bits required to make UUIDs and
dmraid devices work properly?
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Kay,
As requested:
[EMAIL PROTECTED]:~$ sudo dd if=/dev/sda1 count=2 | hexdump -C
2+0 records in
2+0 records out
1024 bytes (1.0 kB) copied, 0.00038136 seconds, 2.7 MB/s
eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS.|
0010 00 00 00 00 00 f8 00 00 3f 00 ff 00
Thanks, that's looks like the same data offered by two different kernel devices.
The fix will probably prevent the wrong detection, because the striping of
volumes
make the data we check for unreachable by the scsi device. But there might still
be setups where we can get exactly the same data
Kay:
[EMAIL PROTECTED]:~$ ls -l /dev/.udev/names/*B080F3DA80F3A54E*
total 0
-rw-r--r-- 1 root root 0 2007-10-23 17:57 \x2fblock\x2fdm-1
-rw-r--r-- 1 root root 0 2007-10-23 17:57 \x2fblock\x2fsda\x2fsda1
So, it does seem there are two devices competing for the same name. I'll
try adding that rule
I added ENV{DM_UUID}==dmraid-*, OPTIONS=link_priority=50 to the file
65-dmsetup.rules, just underneath the line ENV{DM_UUID}==?*,
SYMLINK+=disk/by-id/dm-uuid-$env{DM_UUID}, and it didn't make any
difference. Not sure if this is the correct place to add it.
--
UUID's not correctly allocated for
What does:
udevmonitor
print, when you do:
echo add /sys/block/dm-1/uevent
Does the environment contain DM_UUID? Prefixed with dmraid-?
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification because you are a
One second actually, I've just realised I've rebooted since removing
that extra rule. I'll try it again in a sec
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is the output I get from udevmonitor:
UEVENT[1193162136.861547] add /block/dm-1 (block)
UDEV [1193162136.872177] add /block/dm-1 (block)
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification
Oops, sorry, please add --env :)
udevmonitor --env
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This is what I get now, with the extra rule added:
UEVENT[1193163711.005542] add /block/dm-1 (block)
ACTION=add
DEVPATH=/block/dm-1
SUBSYSTEM=block
SEQNUM=2837
MINOR=1
MAJOR=254
UDEV [1193163711.016679] add /block/dm-1 (block)
UDEV_LOG=3
ACTION=add
DEVPATH=/block/dm-1
SUBSYSTEM=block
Oh, we have a patch in dmraid, we thought that would be already merged.
The plain version of dmraid misses the uuids in the dm tables:
http://www.redhat.com/archives/ataraid-list/2006-September/msg1.html
Scott, we may give dm-* volumes by default a higher priority than plain
disks? What do
The problem is that dmraid needs to claim the entire disk, and disallow
all other access to it. In the case of a raid1, you potentially will
see 3 volumes with the same data: the two underlying mirrors and the
mirror dm device. Any access to the underlying disks will be a problem.
In the case of
Sure, what you really want is the kernel not to create the (invalid)
partitions at all for a raid device.
We are working to get media change events for the disk, and we can start
probing for raid setups (currently media changes are not reported, and
probing a main device would store wrong
I think this has more to do with udev so I'm adding it as well.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification because you are a
What is the output of the following:
vol_id /dev/sda1
vol_id /dev/mapper/nvidia_effeccbe1
Also provide:
blkid /dev/sda1
for comparison.
Thanks
** Changed in: udev (Ubuntu)
Importance: Undecided = Medium
Status: New = Incomplete
--
UUID's not correctly allocated for DMRAID
As requested:
[EMAIL PROTECTED]:~$ sudo vol_id /dev/sda1
[sudo] password for chr1s:
ID_FS_USAGE=filesystem
ID_FS_TYPE=ntfs
ID_FS_VERSION=
ID_FS_UUID=B080F3DA80F3A54E
ID_FS_UUID_ENC=B080F3DA80F3A54E
ID_FS_LABEL=
ID_FS_LABEL_ENC=
ID_FS_LABEL_SAFE=
[EMAIL PROTECTED]:~$ sudo vol_id
Kay: any idea why vol_id is picking up a UUID for the dmraid partition
but blkid doesn't?
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Maybe a left-over signature again, we seem to miss the version information.
We should add more consistency checks to NTFS then.
What does:
dd if=/dev/sda1 count=2 | hexdump -C
and
dd if=/dev/mapper/nvidia_effeccbe1 count=2 | hexdump -C
print?
--
UUID's not correctly allocated for DMRAID
I've added a fix to the git tree, which may prevent the wrong NTFS recognition.
Please still provide the hexdump, so we can be sure to have the right fix.
I also wonder if the nvidia dmraid metadata is recognized. What does:
sudo vol_id /dev/sda
print?
Thanks!
--
UUID's not correctly
** Attachment added: fstab
http://launchpadlibrarian.net/10080275/fstab
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
24 matches
Mail list logo
