Volume manager, what am I doing wrong now?

Volume manager, what am I doing wrong now?

Post by Laurence Lindstro » Sun, 09 Feb 1997 04:00:00



The following relates to 2.5/X86/DU3

   I learned Volume Manager when I first got Solaris running
almost a year ago.  I've used it to access floppies in the past.  
Now I can't get it to work.  

   I run "volcheck", the floppy light flashes briefly, as
expected.  

   I've run the following cpio script many times.  This copies
all of the files in the current directory to the floppy.  

     ls | cpio -omv -Hodc -O/vol/dev/rdiskette0/unlabeled

   Now I'm getting the following error message:  

cpio: Cannot open "/vol/dev/rdiskette0/unlabeled" for output
USAGE:
        cpio -i[bcdfkmrstuvBSV6] [-C size] [-E file] [-H hdr] [-I file
[-M msg]] [-R id] [patterns]
        cpio -o[acvABLV] [-C size] [-H hdr] [-O file [-M msg]]
        cpio -p[adlmuvLV] [-R id] directory

   It's not because this is a DOS floppy is it?  From my
experience, cpio just bulls over DOS formats.  I attempt what I
believe is an unnecessary format:

$ format -d /vol/dev/rdiskette0/unlabeled
Searching for disks...done
No permission (or no disks found)!

   Yes, the write enable window is closed.  I can copy files to
this particular floppy using its DOS name, "/floppy0/floppy" I
think it's called, I have it aliased.  

   I took a look at /vol/dev/rdiskette0, and found the contents
to be "no_name", not "unlabeled".  I tried that name, for both
formatting and cpio, no luck.  

   I have only recently started writing DOS floppies.  That
wouldn't have anything to do with my problem, would it?  

   I must be doing something REAL dumb.  Anybody?  

                                                         Thanks
                                                         Larry

 
 
 

Volume manager, what am I doing wrong now?

Post by Mr. Wh » Mon, 10 Feb 1997 04:00:00


<<<<< Huge portion of this post deleted. >>>>>

Quote:

>    I took a look at /vol/dev/rdiskette0, and found the contents
> to be "no_name", not "unlabeled".  I tried that name, for both
> formatting and cpio, no luck.

>    I have only recently started writing DOS floppies.  That
> wouldn't have anything to do with my problem, would it?

>    I must be doing something REAL dumb.  Anybody?

>                                                          Thanks
>                                                          Larry

Larry,

I'm by no means an expert on suns vold.  But it sounds like you've
hit the nail on the head....  When you're doing a cpio it's expecting
to be able to access a raw device and isn't working on the DOS
formatted floppy.

Have you tried the following:

1.  mount   <this shows where the DOS floppy gets mounted>
2.  ls | cpio -pdmvu  <floppy mount point>

Alternatively try a copy

--
       ___________________________________
      / Mr. Who is:                      /\


   /                                  / /
  /  Technology: no place for wimps! / /
  \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

 
 
 

1. Mounting Volume Manager File Systems without the Volume Manager software

Hi

I have an Enterprise 450 with Solaris 2.6 loaded and a A1000 disk
array attached to it. Right now, the Sun Storage Volume Manager is
installed and all the file systems are created with volume manager.

I am trying to install Solaris 2.8 on a new disk I placed internally
into the 450, so that I can dual boot the system to either 2.6 or 2.8.
However I just found out that I don't have the media for the Volume
Manager and now I am stuck. If I boot into Solaris 2.8, is there
anyway I can mount those file systems created under Solaris 2.6 using
Volume Manager? I tried to copy over those vx drivers and files,
recreated the devices files using mknod but has not been able to bring
up Volume Manager under 2.8.

Is there anything else I can try so that I can mount those file system
when I boot into Solaris 2.8?

Thanks
...
ling

2. Appointment: UNIX administrator, London

3. Difference between veritas volume manager and Sun StorEdge volume manager?

4. ANNOUNCE: Backup.sh - Multiplatform Backup Utility...

5. Upgrade from Solaris 2.6 with Volume Manager 2.6 to Solaris 8 with Volume Manager 3.2

6. socket connection timrout values

7. Sun Volume Manager/Veritas Volume Manager

8. Adding path for shared Libraries?

9. (Issue) Upgrade from Sun Enterprise Volume Manager to Veritas Volume Manager

10. Solaris 9 volume manager OR Veritas volume manager ?

11. Solaris9 Volume Manager Vs Veritas Volume Manager

12. Veritas Volume Manager vs Sun Volume Manager

13. (Issue) Upgrade from Sun Enterprise Volume Manager to Veritas Volume Manager