Sponsored Content
Full Discussion: Soloaris 8/ufsdump error
Special Forums Hardware Filesystems, Disks and Memory Soloaris 8/ufsdump error Post 44833 by jsilva on Thursday 11th of December 2003 08:35:01 AM
Old 12-11-2003
Hi,

The ufsdump should be used on a idle filesystem...
It seems that your /usr/local filesystem is corrupted, unmount /dev/rdsk/c2t5d0s6 and try to fsck it.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Ufsdump

I want to try using Ufsdump for backups . The man pages state that the file systems should be inactive or be in the unmounted state . But for that system should be in single User mode. My query is that can we perform Ufsdump in run-level 3 ? And if no should I have to reboot it in Single user... (3 Replies)
Discussion started by: DPAI
3 Replies

2. UNIX for Dummies Questions & Answers

ufsdump

hi i would like to backup my OS what is the exact command to do? beside backup to tapes can i back up to a directory in another server? will the command be the same? thanks. :confused: (4 Replies)
Discussion started by: legato
4 Replies

3. Solaris

UFSDUMP info

Hi,,,,, My question is : i have to backup a file system of size 92 GB /dev/dsk/c1t1d0s2 135G 92G 41G 70% /data i use the command : ufsdump 0cfu /backup/c1t1d0s2 /dev/rdsk/c1t1d0s2 ...... the output file of the backup is only 2 GB it's normal ?? or i have do a... (0 Replies)
Discussion started by: tt155
0 Replies

4. Solaris

ufsdump

Hi, I want to how to take backup of File system From Disk to Disk using ufsdump? Wheather we can take the backup of root file system from one disk to another if tape drive is not available? wheather it is reliable to restore root file system? (2 Replies)
Discussion started by: manoj.solaris
2 Replies

5. UNIX for Advanced & Expert Users

ufsdump and restore

I just completed a level 0 ufsdump of the following files:- ufsdump 0uf /dev/rmt/0n / ufsdump 0uf /dev/rmt/0n /usr ufsdump 0uf /dev/rmt/0n /export/home ufsdump 0uf /dev/rmt/0n /oracle ufsdump 0uf /dev/rmt/0n /sapr3 I need to restore ALL the files onto a different machine and continue... (1 Reply)
Discussion started by: charleywasharo
1 Replies

6. Solaris

Using ufsdump and ufsrestore

HI Gurus, I have a sunfire V445 server running SAP ECC 6.0 with an Oracle database on Solaris 9 (SunOS 5.9). I recently completed a ufsdump to tape of the following files:- /, /usr, /oracle, /export, /sapr3, I want to restore these files from tape onto a different server of the same... (5 Replies)
Discussion started by: charleywasharo
5 Replies

7. UNIX for Dummies Questions & Answers

Ufsdump

Hi, I have 5 soraris boxes and i am trying to backup all to SAN.Which backup is more suitable tar or ufsdump? Also pls mention what are the important folders i need to back up. Thanks (3 Replies)
Discussion started by: solaris5.10
3 Replies

8. Solaris

ufsdump a dir?

Is there a way to backup a single directory with ufsdump, or is tar better for that? (1 Reply)
Discussion started by: orange47
1 Replies

9. Solaris

ufsdump

Experts, Before patching am advised to take backup : so am going with: ufsdump -0uf /dev/rmt0 / ---> to take the whole / bkp to tape. some servers have /var in diff slice, In this case whether i need to take backup of /var also in tape? ufsdump -ouf /dev/rmt0 /var ---> to take... (3 Replies)
Discussion started by: fizan
3 Replies

10. Solaris

Ufsdump and migration

Hi all, I have a Solaris 10 running on a M4000. I wanted to migrate it to M10 q1) can I do a ufsdump on / in the m4000 and restore it on the m10 ? q2) how do we ufsrestore on the naked M10 without any OS being install/running in the 1st place ? q3) if the answer to the... (5 Replies)
Discussion started by: javanoob
5 Replies
DUMP(5) 							File Formats Manual							   DUMP(5)

NAME
dump, ddate - incremental dump format SYNOPSIS
#include <sys/types.h> #include <sys/ino.h> #include <dumprestor.h> DESCRIPTION
Tapes used by dump and restor(8) contain: a header record two groups of bit map records a group of records describing directories a group of records describing files The format of the header record and of the first record of each description as given in the include file <dumprestor.h> is: #if UCB_NKB == 1 #define NTREC 10 #endif #ifndef UCB_NKB #define NTREC 20 #endif #define MLEN 16 #define MSIZ 4096 #define TS_TAPE 1 #define TS_INODE 2 #define TS_BITS 3 #define TS_ADDR 4 #define TS_END 5 #define TS_CLRI 6 #define MAGIC (int)60011 #define CHECKSUM (int)84446 struct spcl { int c_type; time_t c_date; time_t c_ddate; int c_volume; daddr_t c_tapea; ino_t c_inumber; int c_magic; int c_checksum; struct dinodec_dinode; int c_count; char c_addr[BSIZE]; } spcl; struct idates { char id_name[16]; char id_incno; time_t id_ddate; }; NTREC is the number of BSIZE (sys/param.h) byte records in a physical tape block. MLEN is the number of bits in a bit map word. MSIZ is the number of bit map words. The TS_ entries are used in the c_type field to indicate what sort of header this is. The types and their meanings are as follows: TS_TAPE Tape volume label TS_INODE A file or directory follows. The c_dinode field is a copy of the disk inode and contains bits telling what sort of file this is. TS_BITS A bit map follows. This bit map has a one bit for each inode that was dumped. TS_ADDR A subrecord of a file description. See c_addr below. TS_END End of tape record. TS_CLRI A bit map follows. This bit map contains a zero bit for all inodes that were empty on the file system when dumped. MAGIC All header records have this number in c_magic. CHECKSUM Header records checksum to this value. The fields of the header structure are as follows: c_type The type of the header. c_date The date the dump was taken. c_ddate The date the file system was dumped from. c_volume The current volume number of the dump. c_tapea The current number of this (512-byte) record. c_inumber The number of the inode being dumped if this is of type TS_INODE. c_magic This contains the value MAGIC above, truncated as needed. c_checksum This contains whatever value is needed to make the record sum to CHECKSUM. c_dinode This is a copy of the inode as it appears on the file system; see filsys(5). c_count The count of characters in c_addr. c_addr An array of characters describing the blocks of the dumped file. A character is zero if the block associated with that character was not present on the file system, otherwise the character is non-zero. If the block was not present on the file system, no block was dumped; the block will be restored as a hole in the file. If there is not sufficient space in this record to describe all of the blocks in a file, TS_ADDR records will be scattered through the file, each one picking up where the last left off. Each volume except the last ends with a tapemark (read as an end of file). The last volume ends with a TS_END record and then the tape- mark. The structure idates describes an entry of the file /etc/ddate where dump history is kept. The fields of the structure are: id_name The dumped file system is `/dev/id_nam'. id_incno The level number of the dump tape; see dump(8). id_ddate The date of the incremental dump in system format see types(5). FILES
/etc/ddate SEE ALSO
filsys(5), types(5), dump(8), dumpdir(8), restor(8) 3rd Berkeley Distribution DUMP(5)
All times are GMT -4. The time now is 09:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy