Location of /stand mount point ?

[eric lipede_1]

Torsten ...you realize that this isnt "my" system. I am as surprised as you. What I am trying to do is to unravel the mess.

So, what do you think the fix is ?
thks

[Torsten.]

I'm quite sure replacing lvol12 by lvol1 in fstab will fix it after a reboot.

[eric lipede_1]

Thks !

[Torsten.]

But as a first step I would mount LVOL1 to a temp. mount point and check the contents and health.

[eric lipede_1]

Good idea, I also noticed that its got bad block to "on"

[eric lipede_1]

Interesting ....I mounted it to test and compared ..

test# ll
total 119968
drwxr-xr-x 5 root sys 8192 Mar 15 2009 backup
dr-xr-xr-x 3 bin bin 96 Sep 8 2004 boot.sys
-rw-r--r-- 1 root sys 21 Apr 4 2006 bootconf
lrwxr-xr-x 1 root root 14 Mar 15 2009 bootfs -> current/bootfs
drwxr-xr-x 5 root root 8192 Oct 21 2006 crashconfig
drwxr-xr-x 5 root sys 8192 Mar 15 2009 current
-rw-r--r-- 1 root sys 15296 Mar 15 2009 ioconfig
-r--r--r-- 1 root sys 82 Sep 8 2004 kernrel
drwxr-xr-x 2 root sys 96 Mar 15 2009 krs
drwxr-xr-x 5 root sys 8192 Sep 8 2004 last_install
drwxr-xr-x 2 root root 96 Apr 4 2006 lost+found
lrwxr-xr-x 1 root root 7 Mar 15 2009 nextboot -> current
-rw------- 1 root root 12 Mar 15 2009 rootconf
lrwxr-xr-x 1 root root 15 Mar 15 2009 system -> nextboot/system
-r--r--r-- 1 root sys 2691 Apr 4 2006 system.import
-rw-r--r-- 1 root sys 3982 Nov 23 2008 system.prev
-rwxr-xr-x 2 root sys 61333200 Mar 15 2009 vmunix
test# ll /stand
total 121142
drwxr-xr-x 5 root sys 1024 Aug 23 2009 backup
dr-xr-xr-x 3 root sys 96 Mar 15 2009 boot.sys
-rw-r--r-- 1 root sys 21 Mar 15 2009 bootconf
lrwxr-xr-x 1 root root 14 Nov 26 23:35 bootfs -> current/bootfs
drwxr-xr-x 5 root sys 1024 Mar 15 2009 crashconfig
drwxr-xr-x 4 root root 1024 Nov 26 23:36 current
-rw-r--r-- 1 root sys 15816 Dec 5 08:09 ioconfig
-r--r--r-- 1 root sys 82 Mar 15 2009 kernrel
drwxr-xr-x 2 root sys 96 Nov 26 23:37 krs
drwxr-xr-x 5 root sys 1024 Mar 15 2009 last_install
drwxr-xr-x 2 root root 96 Mar 15 2009 lost+found
drwxr-xr-x 5 root root 1024 Nov 26 23:36 nextboot
-rw------- 1 root sys 12 Nov 26 23:35 rootconf
lrwxr-xr-x 1 root root 15 Nov 26 23:35 system -> nextboot/system
-r--r--r-- 1 root sys 2691 Mar 15 2009 system.import
-rw-r--r-- 1 root root 3952 Apr 3 2009 system.prev
-rwxr-xr-x 3 root sys 61992696 Aug 23 2009 vmunix

so ... according to uptime (up 33 days) the prev vmunix came from the now unmount lvol1

mmmmm!

[Torsten.]

I guess the reason for this was somebody felt lvol1 was just too small.

This is IMHO the most likely reason for this.



So somebody was creating a new LVOL and copied all the contents. So when you create a new kernel for whatever reason, it is in lvol12, but the system always boots from lvol1.



The final solution would be to activate lvol1 again, do an ignite backup, restore the backup and increase the size of lvol1 during this process.

[eric lipede_1]

..yes ...thats the most likely scenario !
Thks to all for the input

[eric lipede_1]

.

[Hakki Aydin Ucar]

>/dev/vg00/lvol13 557056 253845 284277 47% /stand

>/dev/vg00/lvol12 /stand vxfs tranflush 0 1

They are weird ,if you issue the command bdf in the same server ? must be lvol12 not lvol13 in this case..