Am Mittwoch, den 03.12.2008, 12:03 -0500 schrieb Phillip Susi:
> Is this allowed? It looks like you can create a target with a space in
> the name, but then you can not refer to it in a rule of another target.
> Specifically I am seeing a user with a dmraid setup with raid volumes
> using spaces in the name, and dmraid manages to create the stripe target
> ( /dev/mapper/foo bar ), but then can not create the linear mapping on
> top of it for the partition, because the table looks like it has too
> many arguments due to the space.
What you describe here, is essentially caused by bogus names in vendor
metadata not being detected and handled properly by dmraid.
Which metadata format is that being caused by ?
Can you send me the metadata sample retrieved via "dmraid -rD"
(bzip2/tar the resulting *.{dat,offset,size} files before sending) ?
> So should you just avoid doing this,
Yes, whitespace is not to be supported in mapped device names.
> or should the kernel be fixed to
> understand quotes or backslash escapes or something to allow spaces in
> the target device file name?
No M$ worries, please ;)
Heinz
>
> --
> dm-devel mailing list
> dm-devel@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/dm-devel
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
