| 1 |
Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
|
| 3 |
> or something like this with star: |
| 4 |
> |
| 5 |
> star -copy -p -xdot -xattr -H=exustar -sparse -M -C /home . /mnt/new_partition |
| 6 |
> |
| 7 |
> (You can use -V -pat=File1 to exclude files or directories with star, use the |
| 8 |
> -M option to avoid following mount points). |
| 9 |
|
| 10 |
star -copy by default uses the star "-dump" format which is the "exustar" |
| 11 |
format + extended dump metadata. There is no need to specify the archive format |
| 12 |
with star -copy. |
| 13 |
|
| 14 |
Also note that star by default uses a safe extract method that calls fsync(2) |
| 15 |
at the end of each single file extract. This is the only way for star for being |
| 16 |
able to detect all possible extract problems. On Linux, the file system buffer |
| 17 |
cache is implemented in a very inefficient way and with some COW filesystems |
| 18 |
(like ZFS), a fsync(2) is an expensive instruction. In such cases, you may call |
| 19 |
star with the -no-fsync option and switch star to the same level of "safeness" |
| 20 |
as other software to speed up the extract or copy operation. |
| 21 |
|
| 22 |
So if you are on Linux and use star -no-fsync, you will not be less secure than |
| 23 |
other software but get aprox. 20% better performance than with other copy |
| 24 |
methods. |
| 25 |
|
| 26 |
Jörg |
| 27 |
|
| 28 |
-- |
| 29 |
EMail:joerg@××××××××××××××××××××××××.de (home) Jörg Schilling D-13353 Berlin |
| 30 |
js@××××××××××××.de (uni) |
| 31 |
joerg.schilling@××××××××××××××××.de (work) Blog: http://schily.blogspot.com/ |
| 32 |
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily |
Archives