Sponsored Content
Full Discussion: tegsrding VTOC........
Operating Systems Solaris tegsrding VTOC........ Post 302257435 by sudhansu on Wednesday 12th of November 2008 07:00:09 AM
Old 11-12-2008
Bug tegsrding VTOC........

hi all.........

if my VTOC is corrupt or deleted then what to do.....is there any method to reconfigure that........

my second question is , how to see the data block and super block .....

my third question is what is the difference between raw device & block device....
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

To display VTOC information

Hello everybody! 1. Can someone explain, how to obtain the information about every logical volume in the system? 2. And then list vtoc on every volume in the system? O.S.: UnixWare 7.1.* shell: ksh (1 Reply)
Discussion started by: gold4u
1 Replies

2. UNIX for Dummies Questions & Answers

backing up the vtoc

Can you backup the vtoc, then restore it if you somehow mess it up? This is solaris 9, x86. (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

3. Solaris

no VTOC problem

I am using Solaris 10. I restart it today because it halts during working. When i restart it then there is nothing. No Operating system found. I try to boot from Solaris 10 CD but it shows a single disk but there were two operating systems Solaris 10 and windows Xp. There is now only on complete... (2 Replies)
Discussion started by: mansoorulhaq
2 Replies

4. Solaris

after ZFS can not restore VTOC of disk..

I tried to use zfs .. only for test ..so when I take my test disks into zfs pool their VTOC changed .. and 7th slice does not appear now. How can I restore default VTOC to my disks. my machine is x86 .. SunFire X4200 .. so this disks do not have slices like sparc machines .. they have... (6 Replies)
Discussion started by: samar
6 Replies

5. Solaris

Remove VTOC.

Hi, Does anyone know how I can remove the VTOC from a disk. I'm trying to initialize this disk under VxVM but it won't let me as there is still a VTOC present on the disk. I don't want to encapsulate the disk. I just want to have a raw disk that I can play with. Any ideas? Thanks. (5 Replies)
Discussion started by: gwhelan
5 Replies

6. Solaris

Labeling VTOC

How to relabeling the disk VTOC if i relabel the disk the previous data is available or not (5 Replies)
Discussion started by: chandu.bezawada
5 Replies

7. Solaris

Live Upgrade Patching Error: Unable to write vtoc

Attempting to patch several servers using live upgrade Release: Oracle Solaris 10 8/11 s10x_u10wos_17b X86 Error I'm receiving is in the message in the log below tail -15 /var/svc/log/rc6.log Legacy init script "/etc/rc0.d/K50pppd" exited with return code 0. Executing legacy init... (5 Replies)
Discussion started by: Siralos
5 Replies

8. Solaris

Can ufsdump create files that have a .vtoc and .dmp extension?

Hello, I was handed the job of restoring a drive on a old Sun Micro server running Solaris 8. The person who created the backup files told me I would need to use UFSrestore to restore the drive. I have read about everything on ufsrestore that is on this forum and have a decent grasp on how it... (18 Replies)
Discussion started by: CurtArnold
18 Replies
RAW(8)							      System Manager's Manual							    RAW(8)

NAME
raw - bind a Linux raw character device SYNOPSIS
raw /dev/raw/raw<N> <major> <minor> raw /dev/raw/raw<N> /dev/<blockdev> raw -q /dev/raw/raw<N> raw -qa DESCRIPTION
raw is used to bind a Linux raw character device to a block device. Any block device may be used: at the time of binding, the device driver does not even have to be accessible (it may be loaded on demand as a kernel module later). raw is used in two modes: it either sets raw device bindings, or it queries existing bindings. When setting a raw device, /dev/raw/raw<N> is the device name of an existing raw device node in the filesystem. The block device to which it is to be bound can be specified either in terms of its major and minor device numbers, or as a path name /dev/<blockdev> to an existing block device file. The bindings already in existence can be queried with the -q option, with is used either with a raw device filename to query that one device, or with the -a option to query all bound raw devices. Once bound to a block device, a raw device can be opened, read and written, just like the block device it is bound to. However, the raw device does not behave exactly like the block device. In particular, access to the raw device bypasses the kernel's block buffer cache entirely: all I/O is done directly to and from the address space of the process performing the I/O. If the underlying block device driver can support DMA, then no data copying at all is required to complete the I/O. Because raw I/O involves direct hardware access to a process's memory, a few extra restrictions must be observed. All I/Os must be cor- rectly aligned in memory and on disk: they must start at a sector offset on disk, they must be an exact number of sectors long, and the data buffer in virtual memory must also be aligned to a multiple of the sector size. The sector size is 512 bytes for most devices. Use the /etc/sysconfig/rawdevices file to define the set of raw device mappings automatically created during the system startup sequence. The format of the file is the same used in the command line with the exception that the "raw" command itself is omitted. OPTIONS
-q Set query mode. raw will query an existing binding instead of setting a new one. -a With -q , specifies that all bound raw devices should be queried. -h provides a usage summary. BUGS
The Linux dd (1) command does not currently align its buffers correctly, and so cannot be used on raw devices. Raw I/O devices do not maintain cache coherency with the Linux block device buffer cache. If you use raw I/O to overwrite data already in the buffer cache, the buffer cache will no longer correspond to the contents of the actual storage device underneath. This is deliberate, but is regarded either a bug or a feature depending on who you ask! AUTHOR
Stephen Tweedie (sct@redhat.com) Version 0.1 Aug 1999 RAW(8)
All times are GMT -4. The time now is 07:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy