Re: corrupt block in ASM disk
From: onedbguru <onedbguru_at_yahoo.com>
Date: Mon, 2 May 2011 19:35:42 -0700 (PDT)
Message-ID: <ff0a11d7-5655-415b-ba44-d851d09e9709_at_32g2000vbe.googlegroups.com>
On May 1, 11:05 am, lsllcm <lsl..._at_gmail.com> wrote:
> Hi Onedbguru,
>
> Why partition like below:
>
> <!-----
> I typically will partition the device such that:
> p1 = first block block 1 to block 1
> p2 = rest of the device (block 2 to the end)
> ----->
>
> Thanks
Date: Mon, 2 May 2011 19:35:42 -0700 (PDT)
Message-ID: <ff0a11d7-5655-415b-ba44-d851d09e9709_at_32g2000vbe.googlegroups.com>
On May 1, 11:05 am, lsllcm <lsl..._at_gmail.com> wrote:
> Hi Onedbguru,
>
> Why partition like below:
>
> <!-----
> I typically will partition the device such that:
> p1 = first block block 1 to block 1
> p2 = rest of the device (block 2 to the end)
> ----->
>
> Thanks
Some OS's use the first block to store the VTOC (Solaris Volume Table of Contents as an example ). If you overwrite this with ASM information, you may no longer be able to access your the device. So, I just make it a point to ensure that the OS won't do something silly with my devices by reserving that first block.
In using ASM on a Solaris environment, when we did not reserve that first block we would test by doing " dd if=/dev/zero of=/dev/... bs=8192 count=10 ". The first time you do it, it works. Subsequent attempts fail with I/O errors. Next, you have the SA re-enable the device by reformatting it. So, bottom line is to use a standard procedure that works on all platforms. Received on Mon May 02 2011 - 21:35:42 CDT