Error message? you don't get an error message! No, it justs locks root so you can't write anything to it and that's that! Had to reboot to get out of it. You can't growfs on /usr either!
Thanks Annihilannic
Yes I've done that, it's mirrored so I grew my slice on one mirror, then the other, that all went OK but I hadn't realised (or read the man page properly) that I couldn't growfs root. hence the question about booting from CD to do so!
I need to "grow" /. I know that I can't run a growfs on / as it is mounted but if I was to boot from CD would / be mounted (I don't think so) in which case could I successfully run growfs ?
Locale reports it as installed and gives the same result for both a working & failing system. What I was after was some simple sort of test of the locale to verify it's successful use.
Running SAP on a Solaris box & it (SAP) reports that de locale isn't properly installed. Is there a simple way to verify the locale installation to prove SAP wrong?
Compaq Proliant 1600 - needs both a token Ring adapter to connect to an ISDN router and a standard ethernet NIC to connect to the LAN.
The problem we have at the moment is that each time the server boots it 'loses' the token ring interface. That is to say, an IPCONFIG shows only the one...
No no messages or anything. I've had a more experienced colleague look at it and he says he's seen something like it before where an entry somewhere in memory hasn't been dropped. We've tested everything we can think of and it appears to be reading & writing to the volume OK so we are going to...
No there is no vxfstab.
mount shows
/usr/local on /dev/dsk/c0t0d0s6 read/write/setuid/intr/largefiles/onerror=panic/dev=800006 on Fri Oct 15 18:46:05 2004
/usr/local on /dev/vx/dsk/rootdg/usrlocal read/write/setuid/intr/largefiles/onerror=panic/dev=310000c on Sun Feb 20 12:40:20
2005
having cd to / I get the following.
# fuser /dev/dsk/c0t0d0s6
/dev/dsk/c0t0d0s6:
# umount /dev/dsk/c0t0d0s6
umount: /dev/dsk/c0t0d0s6 busy
# umount -f /dev/dsk/c0t0d0s6
umount: /dev/dsk/c0t0d0s6 busy
HELP!
Yesterday I moved our /usr/local file system from /dev/dsk/c0t0d0s6 to /dev/vx/dsk/rootdg/usrlocal. I created the newfs etc and copied all the data and I thought it was job done, but this morning I notice I have 2 entries in df -k
/dev/dsk/c0t0d0s6 984559 614444 311042 67%...
If only it were that simple. The hardware is 100 miles away on a customer site and down time isn't that easy to come by - I was hopeing to narrow it down remotely if that's possible.
I'm getting loads of errors in the messages file about writing to disks but there is no apparent problem with any individual disk. They are all on the same controller c1 Any suggestions as to how I go about determining where the problem lies?
Feb 9 09:16:00 tulip scsi: [ID 107833...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.