| 1 |
On Tuesday 02 October 2007, Mark Kirkwood wrote: |
| 2 |
> $ mkfs.xfs /dev/sda9 |
| 3 |
> $ mkdir /xfsrestore |
| 4 |
> $ mount /dev/sda9 /xfsrestore |
| 5 |
> $ cd /xfsrestore |
| 6 |
> $ tar -jxvf xfsdump-2.2.45.tbz2 |
| 7 |
> $ cd usr/bin |
| 8 |
> $ rm xfsdump xfsrestore |
| 9 |
> $ ln -s /xfsrestore/sbin/xfsdump xfsdump |
| 10 |
> $ ln -s /xfsrestore/sbin/xfsrestore xfsrestore |
| 11 |
> $ export PATH=$PATH:/xfsrestore/sbin:/xfsrestore/usr/bin |
| 12 |
> |
| 13 |
> |
| 14 |
> 5. Restore dumps |
| 15 |
> |
| 16 |
> Use the contents of df.out to figure out which dump should be |
| 17 |
> restored on which device! then temporily mount each filesystem and |
| 18 |
> restore it. |
| 19 |
|
| 20 |
First of all, thanks for sharing. |
| 21 |
|
| 22 |
I used to think xfs was overkill for /boot, but the procedure described |
| 23 |
is quite straightforward. |
| 24 |
|
| 25 |
There are two things I don't understand: |
| 26 |
|
| 27 |
1) why do you delete xfsdump and xfsrestore in /xfsrestore/usr/bin/ just |
| 28 |
extracted to link them to /xfsrestore/sbin |
| 29 |
|
| 30 |
2) the use of df.out isn't clear to me, isn't the dump file name enough |
| 31 |
to know what is in there? |
| 32 |
|
| 33 |
Ciao |
| 34 |
Francesco |
| 35 |
|
| 36 |
-- |
| 37 |
Linux Version 2.6.22-gentoo-r8, Compiled #1 PREEMPT Fri Sep 28 19:41:21 |
| 38 |
CEST 2007 |
| 39 |
One 1GHz AMD Athlon 64 Processor, 2GB RAM, 2003.99 Bogomips Total |
| 40 |
aemaeth |
| 41 |
-- |
| 42 |
gentoo-user@g.o mailing list |
Archives