On Wed, 18 Feb 2015 13:12:09 -0500 Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> wrote: > Jes.Sorensen@xxxxxxxxxx writes: > > From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> > > > > I have received some issues for when creating an array using a > > /dev/mdX name, the matching symlink in /dev/md/X isn't > > created. Whereas if you create /dev/md/X, /dev/mdX is created > > automatically. > > > > I was trying to see if there was a better way of dealing with this, > > but I couldn't find one. If you have suggestions for a better solution > > I am all ears. > > > > Thoughts? > > Hi Neil, > > Any thoughts on this one? Thanks for the reminder.... I'm not sure that I really see the problem. "I ask it to create /dev/mdX and it doesn't create /dev/md/X". Well ... no. You didn't ask it to. If you want it to create /dev/md/X, then ... ask it to. /dev/mdX is the canonical name. It always gets created. /dev/md/X is a convenient alias. It gets created if requested. Is there really a problem here worth solving? Maybe I missed something. NeilBrown > > Cheers, > Jes > > > > > Jes > > > > Jes Sorensen (1): > > mddev_create(): choose /dev/md/ name over /dev/mdX > > > > mdopen.c | 6 +++++- > > 1 file changed, 5 insertions(+), 1 deletion(-) > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html
Attachment:
pgpHmxN2o59GH.pgp
Description: OpenPGP digital signature
