This is a discussion on Restoring / partition problem within the Linux Security forums, part of the System Security and Security Related category; I would like to ask how I can restore / partition in Linux. I dump and restore other partition successfully (ext2 ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I would like to ask how I can restore / partition in Linux.
I dump and restore other partition successfully (ext2 and ext3) I tired with an HP SureStore 40/80GB DLT Drive and Compaq 110/220 GB SDLT Drive, but the same result as following: [root@tapetest root]# dump 0uf /dev/st0 / DUMP: Date of this level 0 dump: Fri Jul 4 10:24:28 2003 DUMP: Dumping /dev/sda5 (/) to /dev/st0 DUMP: Added inode 7 to exclude list (resize inode) DUMP: Label: / DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 131489 tape blocks. DUMP: Volume 1 started with block 1 at: Fri Jul 4 10:25:20 2003 DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: Closing /dev/st0 DUMP: Volume 1 completed at: Fri Jul 4 10:26:26 2003 DUMP: Volume 1 133270 tape blocks (130.15MB) DUMP: Volume 1 took 0:01:06 DUMP: Volume 1 transfer rate: 2019 kB/s DUMP: 133270 tape blocks (130.15MB) on 1 volume(s) DUMP: finished in 53 seconds, throughput 2514 kBytes/sec DUMP: Date of this level 0 dump: Fri Jul 4 10:24:28 2003 DUMP: Date this dump completed: Fri Jul 4 10:26:26 2003 DUMP: Average transfer rate: 2019 kB/s DUMP: DUMP IS DONE [root@tapetest root]# restore if /dev/st0 resync restore, skipped 3388 blocks resync restore, skipped 3410 blocks Segmentation fault Only the root partition have this problem, no problem with other partitions. And this problem exists in both ext2 and ext3 system. And during the dump, sprious 8259A interrupt: IRQ7 was dispalyed in the console Brgds, Henry |
|
|||
|
Henry wrote:
> I would like to ask how I can restore / partition in Linux. > I dump and restore other partition successfully (ext2 and ext3) > I tired with an HP SureStore 40/80GB DLT Drive and Compaq 110/220 GB SDLT > Drive, but the same result as following: Boot from a rescue CD, and use restore from that on your old root disk mounted locally. This is part of the old "bootstrap" problem. You need some sort of bootable tool, not booting from the / partition, to allow you to actually *install* the / partition. > Only the root partition have this problem, no problem with other partitions. > And this problem exists in both ext2 and ext3 system. > And during the dump, > sprious 8259A interrupt: IRQ7 > was dispalyed in the console In which case your tape may be screwed: I'm not familiar with that issue, but it raises a question. Why are you using dump/restore when the ext2/ext3 file systems with modern Linux kernels face a risk because dump talks to the blocks on the disk, but not all files have necessarily been written to disk yet: they may be cached in RAM. In the future, I urge you to use tar: it's nearly as fast, and a lot easier to configure. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|