overwritten rootdisk?

Hi,

The dump device on my system was set to /dev/dsk/c0t0d0s7. I have done a savecore -Lv on the system which worked fine. I'm wondering have I overwritten the rootdisk here by mistake? The system is still up but will need to be rebooted due to an error on it. Will it come back up?

If not is there anyway to save it? It's encapsulated using VVM 5.0. Details below. Thanks.

#  prtvtoc /dev/dsk/c0t0d0s7
* /dev/dsk/c0t0d0s7 partition map
*
* Dimensions:
*     512 bytes/sector
*     424 sectors/track
*      24 tracks/cylinder
*   10176 sectors/cylinder
*   14089 cylinders
*   14087 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector
*   143349312 18446744073566202304 18446744073709551615
*    33560448  59448192  93008639
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      2    00  109788864  33560448 143349311
       1      7    00          0  33560448  33560447
       2      5    00          0 143349312 143349311
       3      3    01   93090048  16698816 109788863
       4     15    01   93008640     81408  93090047
       7     14    01          0 143349312 143349311
# more /etc/dumpadm.conf
#
# dumpadm.conf
#
# Configuration parameters for system crash dump.
# Do NOT edit this file by hand -- use dumpadm(1m) instead.
#
DUMPADM_DEVICE=/dev/dsk/c0t0d0s7
DUMPADM_SAVDIR=/var/crash/hostname
DUMPADM_CONTENT=kernel
DUMPADM_ENABLE=yes

Your root fs will be on slice 0, and I really cant see whart you meant by overwriiten. Looks fine

Huh, it doesn't look fine to me. :confused:

Slice 7 is configured the same as slice 1, the whole disk. Slice 0 is inside slice 7. However, savecore reads and does not write from slice 7. By itself, savecore would not overwrite anything. But if the system panics it will write core beginning at sector 0 and it has the ok to use the entire disk. It really should be dumping to slice 1 where it would still start at sector 0 but would be limited to using only the first 16 GB of the disk. If the system has more than 16 GB of memory it will indeed scribble on the root volume during a panic. If the system has less than 16 GB of memory, yes you would get away with this screwy configuration.

At least this is how it looks to me, am I missing something?

Perderabo intended to say that slice 7 is configured the same as slice 2 (not slice 1 ) in his previous post.

yes I did. :o

Sorry, I overlooked this line.
7 14 01 0 143349312 143349311
Anyway, is there a way to remove slice 7 from being used, w/o affecting the OS?

dumpadm -d <device>

Hi All,

Thanks for your replies. The system did not come back up after the savcore was run and the system rebooted. The /var/file system was corrupted which I then had to create a new file system for and replace the data from tape.

I would rather not have the dump device as /dev/dsk/c0t0d0s7 though for obvious reasons. To do a savecore I would need to specify something that isn't in swap as savecore will dump this as well. Can I specify a directory for the dump device? Something like /dump? Please let me know. Thanks.

There is nothing wrong with using one area for swap and dump and savecore only writes a crashdump. Your layout is even worse than I first thought. I assumed you used slice 1 for swap because that is the standard. If you lost /var, something else must be happening. If those tags are accurate:

slice 0 is root
slice 1 is var
slice 2 is backup
slice 3 is swap

The tags you show for slices 4 and 7 are not in /usr/include/sys/vtoc.h so I don't know about them. :confused:

Anyway you may be using slice 1 for /var which would explain why you lost it.