On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: > I can no longer bring up my vinum volume with the vinum read > command: > > vinum read /dev/wd0s1e /dev/wd2s1f > vinum read /dev/wd0s1e > vinum read /dev/wd2s1f > > all come back with > vinum: no drives
Correct. As I explained in detail in my HEADS UP message a couple of days ago, you must now specify drives, not partitions. The correct command might be vinum read /dev/wd0 /dev/wd2 To quote the message: >> One way you can shoot yourself in the foot: the `read' command has >> changed. In the previous version, you specified the name of exactly >> one device containing a vinum partition. This is suboptimal, because >> it doesn't allow you to read multiple configurations, and it doesn't >> allow you to move drives around. In the new version, you *must* >> specify the names of *all* disks containing Vinum partitions. For >> example, if you have Vinum partitions /dev/da1h /dev/da2h /dev/da3h >> /dev/da4h /dev/da5h and /dev/da6h, you might previously have written: >> >> vinum read /dev/da3h >> >> Now you *must* write: >> >> vinum read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 >> >> If you do this wrong, you have the potential to wipe out your on-disk >> configuration. You can avoid this by disabling saving the >> configuration. Do this with the `setdaemon' command: >> >> # vinum >> vinum -> setdaemon 4 >> vinum -> read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 > I understand that all slices belonging to a volume must now be > passed to read, but that doesn't make any difference. Yes it does. As a result of the incorrect read command, you have probably obliterated your configuration. > I've modified /etc/rc to do a vinum create /etc/vinum.conf instead > and that works, but I thought read was the correct commmand. `read' is the correct command. The arguments you supplied are wrong. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
