10-04-2011
You did not physically destroy the disk. You destroyed any data that was in the various partitions on the disk by creating a filesystem on slice 2 which was set to span the whole disk. There is nothing stopping you using disk in the future.
9 More Discussions You Might Find Interesting
1. Solaris
Hi there
I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Discussion started by: hcclnoodles
0 Replies
2. UNIX for Advanced & Expert Users
How can one mirror disk geometry from one hard disk to another in Solaris.
Is disk snapshot same as a mirror? Pls explain. (3 Replies)
Discussion started by: lexusujx
3 Replies
3. Solaris
Not sure why solaris couldn't detect the geometry of a hard disk which has a working OS of winxp pro.
Is it due to the different OS that the partition information is stored in different location?
When I type '"format" it is shown as below,
c3d1 < drive type unknown>... (5 Replies)
Discussion started by: just.srad
5 Replies
4. Solaris
Hi,
Recently I faced with need of analyze root disk. I figured out two possible ways to do it:
1. Practical. Boot from CD and run format
2. Theoretical. Create live upgrade boot environment on another disk, activate it, reboot, unmont all root disk partitions and run format.
I've already... (3 Replies)
Discussion started by: Sapfeer
3 Replies
5. Shell Programming and Scripting
Hi Folks,
I am trying to make a script to assign all diskspace to slice 0, on multiple sized disks. Since the disks are new they may need to be labelled also to avoid the error: Cannot get disk geometry
Below is my code struggling with logic which doesn't seem to be producing the desired... (0 Replies)
Discussion started by: momin
0 Replies
6. Solaris
Hi there,
I am trying to do root volume mirroring on SunFire V210 server. I have two disks in it.First one is c1t0do and second one is c1t1do. Both disks already have partitions in them so I am deleting the partitions of second disk(c1t1do) using format command and selecting cylinder start 0... (2 Replies)
Discussion started by: newbi8321
2 Replies
7. Solaris
we have a ZFS file system that was created as a pool of just one disk (raid on a SAN) when this was created it was done as a whole disk, and so EFI label.
now we want to mount this file system into an LDOM.
my understanding of how ldom's and disk works this is that we can only do this as a... (1 Reply)
Discussion started by: robsonde
1 Replies
8. Solaris
Hi all,
I am using SPARC Solaris 11.1 with EFI labelled disks.
I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs.
EFI labels use sectors and blocks and I am not sure how exactly it works.
From here I can try and create a... (2 Replies)
Discussion started by: selectstar
2 Replies
9. Solaris
Hi,
How to to make a slice and define as ufs from zpool? Please advice me.
Thanks.
---------- Post updated at 01:53 AM ---------- Previous update was at 12:24 AM ----------
Before slice:
Part Tag Flag Cylinders Size Blocks
0 root wm 0 ... (2 Replies)
Discussion started by: mzainal
2 Replies
LEARN ABOUT HPUX
prealloc
prealloc(1) General Commands Manual prealloc(1)
NAME
prealloc - preallocate disk storage
SYNOPSIS
name size
DESCRIPTION
preallocates at least size bytes of disk space for an ordinary file name, creating the file if name does not already exist. The space is
allocated in an implementation-dependent fashion for fast sequential reads and writes of the file.
fails and no disk space is allocated if name already exists and is not an ordinary file of zero length, if insufficient space is left on
disk, or if size exceeds the maximum file size or the file size limit of the process (see ulimit(2)). The file is zero-filled.
DIAGNOSTICS
returns one of the following values upon completion:
0 Successful completion.
1 name already exists and is not an ordinary file of zero length.
2 There is insufficient room on the disk.
3 size exceeds file size limits.
EXAMPLES
The following example preallocates 50000 bytes for the file
WARNINGS
Allocation of file space is highly dependent on current disk usage. A successful return does not indicate how fragmented the file actually
might be if the disk is approaching its capacity.
AUTHOR
was developed by HP.
SEE ALSO
prealloc(2), ulimit(2).
prealloc(1)