Unable to mkfs ona new volume??
in [Solaris]
|
From: Ste on 15 Apr 2008 18:55 Hello all, I've just created a simple volume using command: vxassist -b -g winddg -U fsgen make windarc 1g After this, issuing a newfs reports me No such device root(a)windn2 # newfs /dev/vx/rdsk/winddg/windarchive /dev/vx/rdsk/winddg/windarchive: No such device or address ls -al /dev/vx/rdsk/winddg/windarchive crw------- 1 root root 315,7002 Apr 16 00:24 /dev/vx/rdsk/winddg/windarchive I'm missing a step?? thanks Stefano
From: Darren Dunham on 15 Apr 2008 20:14 Ste <s.c(a)i.net.it> wrote: > vxassist -b -g winddg -U fsgen make windarc 1g > > After this, issuing a newfs reports me No such device > > root(a)windn2 # newfs /dev/vx/rdsk/winddg/windarchive Typo? "windarc" != "windarchive" > /dev/vx/rdsk/winddg/windarchive: No such device or address > > ls -al /dev/vx/rdsk/winddg/windarchive > crw------- 1 root root 315,7002 Apr 16 00:24 > /dev/vx/rdsk/winddg/windarchive Does VxVM report the volume is healthy? # vxprint -ht -g winddg windarchive Do other tools also fail to access? # dd if=/dev/vx/rdsk/windddg/windarchive of=/dev/null count=1 bs=1b # dd if=/dev/vx/dsk/windddg/windarchive of=/dev/null count=1 bs=1b -- Darren Dunham ddunham(a)taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
From: ITguy on 15 Apr 2008 20:24 On Apr 15, 5:55 pm, Ste <s...(a)i.net.it> wrote: > Hello all, > > I've just created a simple volume using command: > > vxassist -b -g winddg -U fsgen make windarc 1g > > After this, issuing a newfs reports me No such device > > root(a)windn2 # newfs /dev/vx/rdsk/winddg/windarchive > /dev/vx/rdsk/winddg/windarchive: No such device or address > > ls -al /dev/vx/rdsk/winddg/windarchive > crw------- 1 root root 315,7002 Apr 16 00:24 > /dev/vx/rdsk/winddg/windarchive > > I'm missing a step?? > > thanks > Stefano 1) Make sure the volume is done building first - check with "vxtask list" and "vxprint -g <dg>" 2) Try to start the volume with "vxvol start" 3) If there aren't any other volumes in the disk group, or if you don't mind un-mounting those volumes, you could try deporting the group and re-importing it. I've seen this probelm when running VxVM 4 with Sun Cluster 3.2. If the vxdg was registered in the cluster then newfs would work just fine. If the vxdg was NOT registered in the cluster I'd get the "no device" error. I never did find a good answer for this problem, but by booting outside the cluster (with "boot -x") I could newfs the volume just fine.
From: Ste on 15 Apr 2008 21:00 Darren Dunham ha scritto: > Ste <s.c(a)i.net.it> wrote: >> vxassist -b -g winddg -U fsgen make windarc 1g windarc is a mistype..was another test. windarchive is correct >> >> After this, issuing a newfs reports me No such device >> >> root(a)windn2 # newfs /dev/vx/rdsk/winddg/windarchive > > Typo? "windarc" != "windarchive" > >> /dev/vx/rdsk/winddg/windarchive: No such device or address >> >> ls -al /dev/vx/rdsk/winddg/windarchive >> crw------- 1 root root 315,7002 Apr 16 00:24 >> /dev/vx/rdsk/winddg/windarchive > > Does VxVM report the volume is healthy? > > # vxprint -ht -g winddg windarchive root(a)windn2 # vxprint -ht -g winddg windarchive V NAME RVG KSTATE STATE LENGTH READPOL PREFPLEX UTYPE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE DC NAME PARENTVOL LOGVOL SP NAME SNAPVOL DCO v windarchive - ENABLED ACTIVE 9412608 SELECT - fsgen pl windarchive-01 windarchive ENABLED ACTIVE 9412608 CONCAT - RW sd winddg01-02 windarchive-01 winddg01 4096000 9412608 0 SUN35100_4 ENA > Do other tools also fail to access? > > # dd if=/dev/vx/rdsk/windddg/windarchive of=/dev/null count=1 bs=1b > # dd if=/dev/vx/dsk/windddg/windarchive of=/dev/null count=1 bs=1b dd if=/dev/vx/rdsk/windddg/windarchive of=/dev/null count=1 bs=1b dd: /dev/vx/rdsk/windddg/windarchive: open: No such file or directory > Ste
From: Ste on 17 Apr 2008 02:41
ITguy ha scritto: > On Apr 15, 5:55 pm, Ste <s...(a)i.net.it> wrote: > 1) Make sure the volume is done building first - check with "vxtask > list" and "vxprint -g <dg>" > 2) Try to start the volume with "vxvol start" > 3) If there aren't any other volumes in the disk group, or if you > don't mind un-mounting those volumes, you could try deporting the > group and re-importing it. root(a)windn2 # vxprint -ht -g winddg windarchive V NAME RVG KSTATE STATE LENGTH READPOL PREFPLEX UTYPE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE DC NAME PARENTVOL LOGVOL SP NAME SNAPVOL DCO v windarchive - ENABLED ACTIVE 9412608 SELECT - fsgen pl windarchive-01 windarchive ENABLED ACTIVE 9412608 CONCAT - RW sd winddg01-02 windarchive-01 winddg01 4096000 9412608 0 SUN35100_4 ENA > > I've seen this probelm when running VxVM 4 with Sun Cluster 3.2. If > the vxdg was registered in the cluster then newfs would work just > fine. If the vxdg was NOT registered in the cluster I'd get the "no > device" error. I never did find a good answer for this problem, but > by booting outside the cluster (with "boot -x") I could newfs the > volume just fine. My SunCluster is 3.1 and Veritas is 3.5,REV=06.21.2002.23.14 But, as storage is mounted by cluster, rebooting the node without being active node in the cluster makes me no see the storage.. Ste |