01-11-2012
Scrapping slices
Hi Admins,
Server is sparc solaris 9
I am new into solaris with little experiemce with SVM.
/dev/dsk/c3t0d1s4 /u05
/dev/dsk/c3t0d1s3 /u02
/dev/dsk/c3t0d1s5 /u11
There are 3 file system created on slices of disk c3t0d1. Now i want to scrap all the slices and mount as a single FS.
What steps i have to follow to achieve the same.
Regards
newsol
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone know if SUN recommends users to install the root parition on 1 single slice or break out the /var , /etc, /opt etc on separate slices?
What if i only have a single hdd that is only 2 GB (1 Reply)
Discussion started by: owls
1 Replies
2. UNIX for Dummies Questions & Answers
How do I create new disk slices taking space from an existing slice? Right now I have slice 6 (/usr) with 16G. I'd like to create slices 5 (/opt) and 7 (/export/home) and steal space from slice 6.
Thanks (3 Replies)
Discussion started by: kmgrady01
3 Replies
3. UNIX for Dummies Questions & Answers
I downloaded the Solaris recommended patched for x86 and tried to install it, but I got the message that I dont have enough disk space. I don't want to install the patches without the option to back out. Anyway I did a df -k and found that my root mount point is in 948MB whereas my /export/home is... (5 Replies)
Discussion started by: dangral
5 Replies
4. Filesystems, Disks and Memory
Can you have a second primary slice on a second hdd?
I know that primary slices are defined in the mbr, but where are all the sub partitions defined at?
From the OBSD installation FAQ:
What exactly is in the PBR? (0 Replies)
Discussion started by: Derrek
0 Replies
5. UNIX for Dummies Questions & Answers
I have a Sun box running Solaris 9.
My root disk was slices too small when it was installed and I am now at 99% capacity for my root partition.
Is it possible, and if so how?, to increase the size of slice 0 and decrease the size of slice 7??
Thanks!
Current partition table... (6 Replies)
Discussion started by: FredSmith
6 Replies
6. Solaris
Good morning to one and all :-) Thank god its Friday, as its bee na rubbish week for me !
So, a quick question. Disks ! Ive got a few local disks, and a few SAN disks used on my solaris server. Whats confusing me, and Im not sure if there's an issue at the SAN end, or my end, regarding the... (3 Replies)
Discussion started by: sbk1972
3 Replies
7. Solaris
Hi all
I'm having difficulty setting up a proper disk structure on a 72GB HDD. The drive was previously part of a zfs pool. The zpool has ben destroyed and now I want to use the disk in a raid 5 array. I need to partition the disk accordingly though.
This is what the partition table currently... (7 Replies)
Discussion started by: notreallyhere
7 Replies
8. Solaris
how do you get start and end sector of a UFS slice? (2 Replies)
Discussion started by: orange47
2 Replies
9. BSD
I need to shrink a UFS slice with NetBSD on SPARC. seems the only way is backup+reformat. can someone please give me exact commands for that? presumably backup is file-by-file instead of sector-by-sector, but how to preserve permissions/dates/attributes.. ? thanks. (0 Replies)
Discussion started by: orange47
0 Replies
10. UNIX for Dummies Questions & Answers
Hello,
I am using solaris 10 x86. my root and backup slices is having same memory 10 GB and same cylinders numbers . My root and backup cylinders ends at same cylinder number 1031. so for creating a new slice i am giving starting cylinder from 1302 and this is giving me error as "out of range" .... (2 Replies)
Discussion started by: bhargav90
2 Replies
i2o_bs(7D) Devices i2o_bs(7D)
NAME
i2o_bs - Block Storage OSM for I2O
SYNOPSIS
disk@local target id#:a through u
disk@local target id#:a through u raw
DESCRIPTION
The I2O Block Storage OSM abstraction (BSA, which also is referred to as block storage class) layer is the primary interface that Solaris
operating environments use to access block storage devices. A block storage device provides random access to a permanent storage medium.
The i2o_bs device driver uses I2O Block Storage class messages to control the block device; and provides the same functionality (ioctls,
for example) that is present in the Solaris device driver like 'cmdk, dadk' on x86 for disk. The maximum size disk supported by i2o_bs is
the same as what is available on x86.
The i2o_bs is currently implemented version 1.5 of Intelligent IO specification.
The block files access the disk using the system's normal buffering mechanism and are read and written without regard to physical disk
records. There is also a "raw" interface that provides for direct transmission between the disk and the user's read or write buffer. A
single read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are
transmitted. The names of the block files are found in /dev/dsk; the names of the raw files are found in /dev/rdsk.
I2O associates each block storage device with a unique ID called a local target id that is assigned by I2O hardware. This information can
be acquired by the block storage OSM through I2O Block Storage class messages. For Block Storage OSM, nodes are created in
/devices/pci#/pci# which include the local target ID as one component of device name that the node refers to. However the /dev names and
the names in /dev/dsk and /dev/rdsk do not encode the local target id in any part of the name.
For example, you might have the following:
/devices/ /dev/dsk name
---------------------------------------------------------------
/devices/pci@0,0/pci101e,0@10,1/disk@10:a /dev/dsk/c1d0s0
I/O requests to the disk must have an offset and transfer length that is a multiple of 512 bytes or the driver returns an EINVAL error.
Slice 0 is normally used for the root file system on a disk, slice 1 is used as a paging area (for example, swap), and slice 2 for backing
up the entire fdisk partition for Solaris software. Other slices may be used for usr file systems or system reserved area.
Fdisk partition 0 is to access the entire disk and is generally used by the fdisk(1M) program.
FILES
/dev/dsk/cndn[s|p]n block device
/dev/rdsk/cndn[s|p]n raw device
where:
cn controller n
dn instance number
sn UNIX system slice n (0-15)
pn fdisk partition(0)
/kernel/drv/i2o_bs i2o_bs driver
/kernel/drv/i2o_bs.conf Configuration file
ATTRIBUTES
See attributes(5)
for descriptions of the following attributes:
+-----------------------------+-----------------------------+
|ATTRIBUTE TYPE |ATTRIBUTE VALUE
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
SEE ALSO
fdisk(1M), format(1M)mount(1M),lseek(2), read(2), write(2), readdir(3C), vfstab(4), acct.h(3HEAD), attributes(5), dkio(7I)
SunOS 5.10 21 Jul 1998 i2o_bs(7D)