09-29-2014
If you well and truly don't want anything to touch that disk, you could remove the device file...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to know how to make a boot disk to get Solaris 7 to load on a intel machine.
I have checked out Sun.Com, but did not understand how to download and convert the files to a disk.
any help would be appericated
thanks
Bobby (2 Replies)
Discussion started by: Youngadmin
2 Replies
2. Shell Programming and Scripting
how to make a line BLINKING in output and also how to increase font size in output
suppose in run a.sh script
inside echo "hello world "
i want that this should blink in the output and also
the font size of hello world should be big ..
could you please help me out in this (3 Replies)
Discussion started by: mail2sant
3 Replies
3. Shell Programming and Scripting
Hi all... I-m quite a new user of UNIX and i was trying to write a simple program and my problem is the following:how can i make a typed letter disappear (as we see in the MORE command, when we type <space>, b, q etc...) i know that for typing some text that has to be read it's used the structure:... (0 Replies)
Discussion started by: Cellofan
0 Replies
4. Solaris
Hi, I want to make sure a local disk c1t1d0s2 is not being used. SVM and VxVM are used on this Solaris 10 systems. This disk can not be found using 'df -k', 'metastat' and 'vxprint -ht'. But I can't mount it though format shows it contains ufs filesystem:
# mount /dev/dsk/c1t1d0s0 /mnt
Aug 18... (5 Replies)
Discussion started by: aixlover
5 Replies
5. Solaris
I'm preparing to recover a Oracle Fire X4170 server in a disaster recovery test at a different location than in prod. I have some questions about fdisk partitions. I'm using Solaris 10 update 10.
On my prod server, the boot disk has 2 partitions, diagnostic and solaris. Is the diagnostic... (1 Reply)
Discussion started by: TKD
1 Replies
6. UNIX for Dummies Questions & Answers
i'm trying to add disk to red hat , use fdisk -l but it doesn't recognize it
what should i do it to get it works? (3 Replies)
Discussion started by: prpkrk
3 Replies
7. BSD
Hello,
MBR partition table made by linux fdisk looks certainly not correct when printed by openbsd fdisk:
Partition table created on linux (centos 6.3):
# fdisk -l /dev/sdc
Disk /dev/sdc: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 *... (2 Replies)
Discussion started by: vilius
2 Replies
8. UNIX for Dummies Questions & Answers
We can Know the storage devices in fdisk -l. But Please tell me how can i identify the SAN devices :wall:
How SAN devices are represented in the fdisk -l output :wall::wall:
Thanks in Advance........:D (3 Replies)
Discussion started by: vamshigvk475
3 Replies
9. Red Hat
Hi,
I'm running a Red Hat Enterprise Linux Server release 5.3 (Tikanga) on VMWare. It is a production system for which I may not get downtime soon. I happened to resize a underlying disk and the changes are not reflecting in the fdisk ouput. Further details are as follows.
The disk which i... (3 Replies)
Discussion started by: maverick_here
3 Replies
10. Shell Programming and Scripting
Hi ,
I am trying to filter out the below output of fdisk -l command :
fdisk -l
Disk /dev/sda: 42.9 GB, 42949672960 bytes
255 heads, 63 sectors/track, 5221 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 ... (9 Replies)
Discussion started by: omkar.jadhav
9 Replies
HP(4) Kernel Interfaces Manual HP(4)
NAME
hp - RH-11/RP04, RP05, RP06 moving-head disk
DESCRIPTION
The octal representation of the minor device number is encoded idp, where i is an interleave flag, d is a physical drive number, and p is a
pseudodrive (subsection) within a physical unit. If i is 0, the origins and sizes of the pseudodisks on each drive, counted in cylinders
of 418 512-byte blocks, are:
disk start length
0 0 23
1 23 21
2 0 0
3 0 0
4 44 386
5 430 385
6 44 367
7 44 771
If i is 1, the minor device consists of the specified pseudodisk on drives numbered 0 through the designated drive number. Successively
numbered blocks are distributed across the drives in rotation.
Systems distributed for these devices use disk 0 for the root, disk 1 for swapping, and disk 4 (RP04/5) or disk 7 (RP06) for a mounted user
file system.
The block files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records.
A `raw' interface provides for direct transmission between the disk and the user's read or write buffer. A single read or write call
results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted. The names of
the raw files conventionally begin with an extra `r.' In raw I/O the buffer must begin on a word boundary, and raw I/O to an interleaved
device is likely to have disappointing results.
FILES
/dev/rp?, /dev/rrp?
SEE ALSO
rp(4)
BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
Raw device drivers don't work on interleaved devices.
HP(4)