File system mounted twice

[snapshot]

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% /usr/local
/dev/vx/dsk/rootdg/usrlocal 984559 614444 311042 67% /usr/local

If I write a file in /usr/local both entries in df -k reflect it. umount -f /dev/dsk/c0t0d0s6 says it's busy. fuser only shows me as active, tried the umount as a rsh command from another box.

Any suggestions as to how to resolve, preferably without bringing this production system down?

 

[KenCunningham]

If you're in the filesystem when trying to unmount it, it will show as busy (a common problem with cd mounts!). Try cding to / and unmount then. Let us know if this works. Have you changed the entry in /etc/vfstab to reflect the change?

 

[snapshot]

Ken

No, tired that!

Yes I changes the entry in vfstab. I'm not sure how I managed to get in this situation!

 

[snapshot]

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

 

[KenCunningham]

Weird (or possibly not if we're dealing with vxfs - is there a vxfstab too, I can't remember?). What does a mount command show you?

 

[snapshot]

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

 

[KenCunningham]

Anything in /var/adm/messages?

As you'll see, I'm running out of ideas here!

 

[snapshot]

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 live with it for now and see if it will sort itself out when we can next unmount everything & reboot - probably next weekend.

Thanks for your help.

 

[KenCunningham]

Thanks - interesting theory. Let us know if the reboot fixes it. Cheers.

 

[comtec17]

When you added the dsk to rootdg how did you migrate the data? It may be possible that vxvm has mirrored the volume.