[opensuse-factory] ¿Which is the better way to clone the btrfs system root partition?
Because I had to reinstall Leap because crashed the hard drive and I had to replace it on the computar of a friend, as my internet connection is slow, I asked a friend to download and record the DVD of the last beta of Leap 42.3. But as the download of the iso my friend made it from windows, the dvd was corrupt, and some of the packages failed in the installation, just like the installation of grub. I choose to install Leap 42.2, and upgrade with the leap 42.3 beta dvd, with the internet connection enabled, and most of the packages were installed from the repositories, but it took about 6 hours to upgrade. As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3. ¿Which is the better way? Both partitions, source and destination has about the same size of about 60 GB (the destination 59.4 GB). Thanks, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-07-23 14:01, Juan Erbes wrote:
Because I had to reinstall Leap because crashed the hard drive and I had to replace it on the computar of a friend, as my internet connection is slow, I asked a friend to download and record the DVD of the last beta of Leap 42.3. But as the download of the iso my friend made it from windows, the dvd was corrupt, and some of the packages failed in the installation, just like the installation of grub.
I recommend using "DownThemAll!", a Firefox plugin, to do the download in Windows. It will automatically verify and correct downloads errors. (recomiendo usar "DownThemAll!", un plugin de Firefox, para descargar en Windows. Automáticamente verificará y corregirá los errores.)
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again. (no existe un buen sistema para clonar una partición raíz btrfs. Es mejor instalar de nuevo) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 23 July 2017 at 15:45, Carlos E. R. <robin.listas@telefonica.net> wrote:
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again.
Carlos, please don't be so inaccurate with your statements when someone is legitimately asking for help Juan, you can use btrfs send and receive to clone a system to another disk. https://www.suse.com/documentation/sles-12/stor_admin/data/sec_filesystems_m... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-07-23 15:51, Richard Brown wrote:
On 23 July 2017 at 15:45, Carlos E. R. <robin.listas@telefonica.net> wrote:
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again.
Carlos, please don't be so inaccurate with your statements when someone is legitimately asking for help
To my knowledge, there is no way to clone a btrfs filesystem. You have to format and manually create the volumes and subvolumes, and there is no listing of which they are on each openSUSE release. The question has been asked several times, and none has answered it adequately. My answer, to my knowledge, is perfectly accurate. It is not the first time I have made the same answer and none has yet proposed a better method during the years.
Juan, you can use btrfs send and receive to clone a system to another disk.
https://www.suse.com/documentation/sles-12/stor_admin/data/sec_filesystems_m...
This does not explain how to clone a btrfs filesystem from scratch. The word "clone" does not even exist in the entire page. It only explains how to copy the files and keep them in sync. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Op zondag 23 juli 2017 16:13:50 CEST schreef Carlos E. R.:
On 2017-07-23 15:51, Richard Brown wrote:
On 23 July 2017 at 15:45, Carlos E. R. <robin.listas@telefonica.net> wrote:
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again.
Carlos, please don't be so inaccurate with your statements when someone is legitimately asking for help
To my knowledge, there is no way to clone a btrfs filesystem. You have to format and manually create the volumes and subvolumes, and there is no listing of which they are on each openSUSE release. The question has been asked several times, and none has answered it adequately.
My answer, to my knowledge, is perfectly accurate. It is not the first time I have made the same answer and none has yet proposed a better method during the years.
Juan, you can use btrfs send and receive to clone a system to another disk.
https://www.suse.com/documentation/sles-12/stor_admin/data/sec_filesystems _major_btrfs.html This does not explain how to clone a btrfs filesystem from scratch. The word "clone" does not even exist in the entire page. It only explains how to copy the files and keep them in sync.
Guess you misread, it makes a copy of the filesystem "Btrfs send/receive Btrfs allows to make snapshots to capture the state of the file system. Snapper, for example, uses this feature to create snapshots before and after system changes, allowing a rollback. However, together with the send/receive feature, snapshots can also be used to create and maintain copies of a file system in a remote location. This feature can, for example, be used to do incremental backups." i.e. have a backup system ready all the time. Nice, very nice, didn't know this feature. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
23.07.2017 18:52, Knurpht - Gertjan Lettink пишет:
Op zondag 23 juli 2017 16:13:50 CEST schreef Carlos E. R.:
On 2017-07-23 15:51, Richard Brown wrote:
On 23 July 2017 at 15:45, Carlos E. R. <robin.listas@telefonica.net> wrote:
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again.
Carlos, please don't be so inaccurate with your statements when someone is legitimately asking for help
To my knowledge, there is no way to clone a btrfs filesystem. You have to format and manually create the volumes and subvolumes, and there is no listing of which they are on each openSUSE release. The question has been asked several times, and none has answered it adequately.
My answer, to my knowledge, is perfectly accurate. It is not the first time I have made the same answer and none has yet proposed a better method during the years.
Juan, you can use btrfs send and receive to clone a system to another disk.
https://www.suse.com/documentation/sles-12/stor_admin/data/sec_filesystems _major_btrfs.html This does not explain how to clone a btrfs filesystem from scratch. The word "clone" does not even exist in the entire page. It only explains how to copy the files and keep them in sync.
Guess you misread, it makes a copy of the filesystem
No, it does not. It copies read-only snapshot of one and only one volume. It can *not* be used to replicate filesystem - for a start, there is no way to replicate top-level subvolume at all. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op zondag 23 juli 2017 18:33:08 CEST schreef Andrei Borzenkov:
23.07.2017 18:52, Knurpht - Gertjan Lettink пишет:
Op zondag 23 juli 2017 16:13:50 CEST schreef Carlos E. R.:
On 2017-07-23 15:51, Richard Brown wrote:
On 23 July 2017 at 15:45, Carlos E. R. <robin.listas@telefonica.net>
wrote:
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again.
Carlos, please don't be so inaccurate with your statements when someone is legitimately asking for help
To my knowledge, there is no way to clone a btrfs filesystem. You have to format and manually create the volumes and subvolumes, and there is no listing of which they are on each openSUSE release. The question has been asked several times, and none has answered it adequately.
My answer, to my knowledge, is perfectly accurate. It is not the first time I have made the same answer and none has yet proposed a better method during the years.
Juan, you can use btrfs send and receive to clone a system to another disk.
https://www.suse.com/documentation/sles-12/stor_admin/data/sec_filesyste ms _major_btrfs.html
This does not explain how to clone a btrfs filesystem from scratch. The word "clone" does not even exist in the entire page. It only explains how to copy the files and keep them in sync.
Guess you misread, it makes a copy of the filesystem
No, it does not. It copies read-only snapshot of one and only one volume. It can *not* be used to replicate filesystem - for a start, there is no way to replicate top-level subvolume at all.
I stand corrected, thanks. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-07-23 12:52 GMT-03:00 Knurpht - Gertjan Lettink <knurpht@opensuse.org>:
Op zondag 23 juli 2017 16:13:50 CEST schreef Carlos E. R.:
On 2017-07-23 15:51, Richard Brown wrote:
On 23 July 2017 at 15:45, Carlos E. R. <robin.listas@telefonica.net> wrote:
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again.
Carlos, please don't be so inaccurate with your statements when someone is legitimately asking for help
To my knowledge, there is no way to clone a btrfs filesystem. You have to format and manually create the volumes and subvolumes, and there is no listing of which they are on each openSUSE release. The question has been asked several times, and none has answered it adequately.
My answer, to my knowledge, is perfectly accurate. It is not the first time I have made the same answer and none has yet proposed a better method during the years.
Juan, you can use btrfs send and receive to clone a system to another disk.
https://www.suse.com/documentation/sles-12/stor_admin/data/sec_filesystems _major_btrfs.html This does not explain how to clone a btrfs filesystem from scratch. The word "clone" does not even exist in the entire page. It only explains how to copy the files and keep them in sync.
Guess you misread, it makes a copy of the filesystem
"Btrfs send/receive Btrfs allows to make snapshots to capture the state of the file system. Snapper, for example, uses this feature to create snapshots before and after system changes, allowing a rollback. However, together with the send/receive feature, snapshots can also be used to create and maintain
copies of a file system in a remote location. This feature can, for example, be
used to do incremental backups."
i.e. have a backup system ready all the time. Nice, very nice, didn't know this feature.
They are many ways to do this job, like: dd if=/dev/sda1 of=/dev/sdb1 bs=1048576 But this riski and it duplicates the UUID of the hard disks. Other more civilized way is with send btrfs: The steps to "clone" /source to /target are: Get a list of subvolumes ordered by ogen: btrfs subvolume list -qu --sort ogen /source. Sorting is probably enough to guarantee that snapshots or subvolumes which depend on previous ones are handled first. This is important for dealing with Copy-on-Write, because we need to have the base volumes transferred first. Make all subvolumes read-only using btrfs property set -ts /source/some-volume ro true. Now, for each subvolume from the list above, starting at the top, do the following: If the volume does not have a parent UUID (displayed as -) or the parent UUID does not exist anymore in the list, run: btrfs send /source/some/volume | btrfs receive /target/some/ If the volume does have a parent UUID which still exists, we should have transferred it already because of --sort ogen and we can use that as a base to avoid data duplication. Hence, find the parent UUID's path in the list and run: btrfs send -p /source/parent/volume/ -c /source/parent/volume/ /source/some/volume/ | btrfs receive /target/some/ (btrfs would probably guess the -p argument automatically, but I prefer to be explicit). After running one of the above commands make the target and source read-write again: btrfs property set -ts /source/some/volume ro false; btrfs property set -ts /target/some/volume ro false. This step can be skipped if the source has been previously read-only. https://superuser.com/questions/607363/how-to-copy-a-btrfs-filesystem another way to clone a Btrfs volume is the seed device. Make A a seed device, and it mounts read-only, add a new device to the volume, then umount and remount, and it mounts read-write, then delete the seed device and data is migrated to the new device. But also, the UUID is unique on the new device. After it's completely, the seed device can be made a non-seed volume again (no longer mounts read only). https://lists.opensuse.org/opensuse/2015-06/msg00694.html Thanks, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-07-23 22:17, Juan Erbes wrote:
They are many ways to do this job, like:
dd if=/dev/sda1 of=/dev/sdb1 bs=1048576
But this riski and it duplicates the UUID of the hard disks.
The risk with dd is that you make a mistake and write to some unintended place and destroy it. Otherwise, it is pretty safe if the partitions are the exact same size. Well, you can probably change the UUID and Label afterwards, which can be done with btrfstune (see man page). The destination can be bigger size, but then you have to grow the filesystem, and this is risky: https://www.suse.com/es-es/support/kb/doc/?id=7018329 https://www.suse.com/documentation/sles-12/singlehtml/stor_admin/stor_admin.... https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-filesystem
Other more civilized way is with send btrfs:
The steps to "clone" /source to /target are:
Get a list of subvolumes ordered by ogen: btrfs subvolume list -qu --sort ogen /source. Sorting is probably enough to guarantee that snapshots or subvolumes which depend on previous ones are handled first. This is important for dealing with Copy-on-Write, because we need to have the base volumes transferred first.
Ah. This seems better. Good find!
https://superuser.com/questions/607363/how-to-copy-a-btrfs-filesystem
Notice that this is a support forum like this. Ie, not a categorical procedure. There is another interesting method here: https://unix.stackexchange.com/questions/63528/how-to-clone-btrfs-filesystem... Still, if your idea is to upgrade the resulting system to a new release, you should still consider installing fresh, because the new release may have a different subvolume structure. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
2017-07-24 8:30 GMT-03:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2017-07-23 22:17, Juan Erbes wrote:
They are many ways to do this job, like:
dd if=/dev/sda1 of=/dev/sdb1 bs=1048576
But this riski and it duplicates the UUID of the hard disks.
The risk with dd is that you make a mistake and write to some unintended place and destroy it. Otherwise, it is pretty safe if the partitions are the exact same size.
Well, you can probably change the UUID and Label afterwards, which can be done with btrfstune (see man page). The destination can be bigger size, but then you have to grow the filesystem, and this is risky:
https://www.suse.com/es-es/support/kb/doc/?id=7018329
https://www.suse.com/documentation/sles-12/singlehtml/stor_admin/stor_admin....
https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-filesystem
Other more civilized way is with send btrfs:
The steps to "clone" /source to /target are:
Get a list of subvolumes ordered by ogen: btrfs subvolume list -qu --sort ogen /source. Sorting is probably enough to guarantee that snapshots or subvolumes which depend on previous ones are handled first. This is important for dealing with Copy-on-Write, because we need to have the base volumes transferred first.
Ah. This seems better. Good find!
https://superuser.com/questions/607363/how-to-copy-a-btrfs-filesystem
Notice that this is a support forum like this. Ie, not a categorical procedure.
I tryed this, but it do'nt worked for me (can be a ignored step)
There is another interesting method here:
https://unix.stackexchange.com/questions/63528/how-to-clone-btrfs-filesystem...
I can try this, but first must execute smartctl on the destination disk, to see if it has phisical damage.
Still, if your idea is to upgrade the resulting system to a new release, you should still consider installing fresh, because the new release may have a different subvolume structure.
In the upgrade procces about 80% of the packages are downloaded from the online repos, because they are newer than the DVD. Regards,. Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Jul 24, 2017 at 2:30 PM, Carlos E. R. <robin.listas@telefonica.net> wrote: ...
Get a list of subvolumes ordered by ogen: btrfs subvolume list -qu --sort ogen /source. Sorting is probably enough to guarantee that snapshots or subvolumes which depend on previous ones are handled first. This is important for dealing with Copy-on-Write, because we need to have the base volumes transferred first.
Ah. This seems better. Good find!
The result won't match original layout exactly, in particular, .snapshots subdirectories will be missing, so you won't be able to even boot (default installation has /etc/fstab entry for /.snapshots mount point). This of course can be fixed up manually, but who knows what else will be missing. And manual fixup will still be different from original. So it is by far not filesystem clone.
https://superuser.com/questions/607363/how-to-copy-a-btrfs-filesystem
Notice that this is a support forum like this. Ie, not a categorical procedure.
There is another interesting method here:
https://unix.stackexchange.com/questions/63528/how-to-clone-btrfs-filesystem...
Well, at the end adding new and removing old device (or simply replacing) is always possible and as long as it runs to completion before reboot it should be the most simple way to migrate btrfs between devices. Target device can be of any size as long as it is large enough for current data amount. Unfortunately there are known issues with multi-device btrfs on startup, which may come unexpected. of course you still will need to re-install bootloader after moving device. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-07-24 13:49, Andrei Borzenkov wrote:
On Mon, Jul 24, 2017 at 2:30 PM, Carlos E. R. <> wrote: ...
Get a list of subvolumes ordered by ogen: btrfs subvolume list -qu --sort ogen /source. Sorting is probably enough to guarantee that snapshots or subvolumes which depend on previous ones are handled first. This is important for dealing with Copy-on-Write, because we need to have the base volumes transferred first.
Ah. This seems better. Good find!
The result won't match original layout exactly, in particular, .snapshots subdirectories will be missing, so you won't be able to even boot (default installation has /etc/fstab entry for /.snapshots mount point). This of course can be fixed up manually, but who knows what else will be missing. And manual fixup will still be different from original. So it is by far not filesystem clone.
Oh :-(
https://superuser.com/questions/607363/how-to-copy-a-btrfs-filesystem
Notice that this is a support forum like this. Ie, not a categorical procedure.
There is another interesting method here:
https://unix.stackexchange.com/questions/63528/how-to-clone-btrfs-filesystem...
Well, at the end adding new and removing old device (or simply replacing) is always possible and as long as it runs to completion before reboot it should be the most simple way to migrate btrfs between devices. Target device can be of any size as long as it is large enough for current data amount. Unfortunately there are known issues with multi-device btrfs on startup, which may come unexpected.
of course you still will need to re-install bootloader after moving device.
Ah, yes. What about partclone.btrfs? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
2017-07-24 8:49 GMT-03:00 Andrei Borzenkov <arvidjaar@gmail.com>:
On Mon, Jul 24, 2017 at 2:30 PM, Carlos E. R. <robin.listas@telefonica.net> wrote: ...
Get a list of subvolumes ordered by ogen: btrfs subvolume list -qu --sort ogen /source. Sorting is probably enough to guarantee that snapshots or subvolumes which depend on previous ones are handled first. This is important for dealing with Copy-on-Write, because we need to have the base volumes transferred first.
Ah. This seems better. Good find!
The result won't match original layout exactly, in particular, .snapshots subdirectories will be missing, so you won't be able to even boot (default installation has /etc/fstab entry for /.snapshots mount point). This of course can be fixed up manually, but who knows what else will be missing. And manual fixup will still be different from original. So it is by far not filesystem clone.
https://superuser.com/questions/607363/how-to-copy-a-btrfs-filesystem
Notice that this is a support forum like this. Ie, not a categorical procedure.
There is another interesting method here:
https://unix.stackexchange.com/questions/63528/how-to-clone-btrfs-filesystem...
Well, at the end adding new and removing old device (or simply replacing) is always possible and as long as it runs to completion before reboot it should be the most simple way to migrate btrfs between devices. Target device can be of any size as long as it is large enough for current data amount. Unfortunately there are known issues with multi-device btrfs on startup, which may come unexpected.
of course you still will need to re-install bootloader after moving device.
I will try with partclone.btrfs http://partclone.org/features/ One of the most interesting features is the option of generate a image file, and I do'nt need to write to the destination HD inmediately, and I have time to purchase a new HD. Thanks, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 24 Jul 2017, Carlos E. R. wrote:
On 2017-07-23 15:51, Richard Brown wrote:
On 23 July 2017 at 15:45, Carlos E. R. <robin.listas@telefonica.net> wrote:
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again.
Carlos, please don't be so inaccurate with your statements when someone is legitimately asking for help
To my knowledge, there is no way to clone a btrfs filesystem. You have to format and manually create the volumes and subvolumes, and there is no listing of which they are on each openSUSE release. The question has been asked several times, and none has answered it adequately.
My answer, to my knowledge, is perfectly accurate. It is not the first time I have made the same answer and none has yet proposed a better method during the years.
Juan, you can use btrfs send and receive to clone a system to another disk.
https://www.suse.com/documentation/sles-12/stor_admin/data/sec_filesystems_m...
This does not explain how to clone a btrfs filesystem from scratch. The word "clone" does not even exist in the entire page. It only explains how to copy the files and keep them in sync.
I started down the road to cloning a btrfs root using btrfs utilities, and in the end the journey convinced me not to use btrfs (and I don't give up easily). In case it helps, I have written up notes on the structure of an openSUSE btrfs root volume and a bit about recreating a root volume: https://forums.opensuse.org/showthread.php/521277-LEAP-42-2-btrfs-root-files... As well as the first post, there is a second post further down the thread concerning preserving copy-on-write attributes. In this case I suspect using a non-btrfs partition cloning utility might be the easiest approach. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-07-25 5:57 GMT-03:00 Michael Hamilton <michael@actrix.gen.nz>:
On Mon, 24 Jul 2017, Carlos E. R. wrote:
On 2017-07-23 15:51, Richard Brown wrote:
On 23 July 2017 at 15:45, Carlos E. R. <robin.listas@telefonica.net> wrote:
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
There is no good way to clone a btrfs root partition. Better install again.
Carlos, please don't be so inaccurate with your statements when someone is legitimately asking for help
To my knowledge, there is no way to clone a btrfs filesystem. You have to format and manually create the volumes and subvolumes, and there is no listing of which they are on each openSUSE release. The question has been asked several times, and none has answered it adequately.
My answer, to my knowledge, is perfectly accurate. It is not the first time I have made the same answer and none has yet proposed a better method during the years.
Juan, you can use btrfs send and receive to clone a system to another disk.
https://www.suse.com/documentation/sles-12/stor_admin/data/sec_filesystems_m...
I tryed this, but is possible I do'nt make a step, and the procces failed.
This does not explain how to clone a btrfs filesystem from scratch. The word "clone" does not even exist in the entire page. It only explains how to copy the files and keep them in sync.
I started down the road to cloning a btrfs root using btrfs utilities, and in the end the journey convinced me not to use btrfs (and I don't give up easily). In case it helps, I have written up notes on the structure of an openSUSE btrfs root volume and a bit about recreating a root volume:
https://forums.opensuse.org/showthread.php/521277-LEAP-42-2-btrfs-root-files...
Very interesting an useful the link. This is a page to save!
As well as the first post, there is a second post further down the thread concerning preserving copy-on-write attributes.
In this case I suspect using a non-btrfs partition cloning utility might be the easiest approach. --
I tryed partclone, and it do'nt generated the FS image file. Tryed later with fsarchiver, it worked fine, but restoring the image of the FS, do'nt created all the subvolumens. Because I replaced the old disk with seven years of use, with a new disk, the next step is with "dd". I know dd can be destructive to the partition table, and I experienced it trying to restore a MBR with dd (emulating the "fdisk /mbr" of DOS), but it destroyed the partition table. Anyway, the hard drive was damaged and it was replaced it in warranty, and is where I installed Leap 42.3, with all the problems which I explained on my first email. At this point, in all the time I lost trying to clone the disk, I could have installed Leap 42.2 and upgraded via the internet with the Leap 42.3 beta DVD damaged, but what I have gained is experience, and to better know what btrfs is and the cloning tools . It would be good if Opensuse included in the yast a cloning and backup tool. Regards, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-07-25 13:30, Juan Erbes wrote:
Because I replaced the old disk with seven years of use, with a new disk, the next step is with "dd". I know dd can be destructive to the partition table, and I experienced it trying to restore a MBR with dd (emulating the "fdisk /mbr" of DOS), but it destroyed the partition table. Anyway, the hard drive was damaged and it was replaced it in warranty, and is where I installed Leap 42.3, with all the problems which I explained on my first email.
Notice that you do not need to touch the partition table at all for your needs. You are to copy a single partition, not the entire disk. Say the the source is /dev/sda5 and the destination is /dev/sdc13. So you do: dd if=/dev/sda5 of=/dev/sdc13 bs=16M There is no danger at all of harming the partition table. If you want to replace the MBR of a disk, you do: dd if=mbr_backup of=/dev/sdX bs=440 count=1 and that will not touch the partition table.
At this point, in all the time I lost trying to clone the disk, I could have installed Leap 42.2 and upgraded via the internet with the Leap 42.3 beta DVD damaged, but what I have gained is experience, and to better know what btrfs is and the cloning tools .
:-D
It would be good if Opensuse included in the yast a cloning and backup tool.
You can use clonezilla... but still, btrfs is a problem. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAll35jAACgkQja8UbcUWM1y3ugD9EFP8/ZDrqWpRRbvVv8uti15a O+ev4aR/qfGfDofjs/kA/RD/wErojRV6bkaLwX88HtRq/ozP+q17oU+W8pGLugtR =XeW7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 25/07/17 08:45 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2017-07-25 13:30, Juan Erbes wrote:
Because I replaced the old disk with seven years of use, with a new disk, the next step is with "dd". I know dd can be destructive to the partition table, and I experienced it trying to restore a MBR with dd (emulating the "fdisk /mbr" of DOS), but it destroyed the partition table. Anyway, the hard drive was damaged and it was replaced it in warranty, and is where I installed Leap 42.3, with all the problems which I explained on my first email.
Notice that you do not need to touch the partition table at all for your needs. You are to copy a single partition, not the entire disk. Say the the source is /dev/sda5 and the destination is /dev/sdc13. So you do:
dd if=/dev/sda5 of=/dev/sdc13 bs=16M
There is no danger at all of harming the partition table.
If you want to replace the MBR of a disk, you do:
dd if=mbr_backup of=/dev/sdX bs=440 count=1
and that will not touch the partition table.
At this point, in all the time I lost trying to clone the disk, I could have installed Leap 42.2 and upgraded via the internet with the Leap 42.3 beta DVD damaged, but what I have gained is experience, and to better know what btrfs is and the cloning tools .
:-D
It would be good if Opensuse included in the yast a cloning and backup tool.
You can use clonezilla... but still, btrfs is a problem.
- -- Cheers / Saludos,
Carlos E. R.
(from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iF4EAREIAAYFAll35jAACgkQja8UbcUWM1y3ugD9EFP8/ZDrqWpRRbvVv8uti15a O+ev4aR/qfGfDofjs/kA/RD/wErojRV6bkaLwX88HtRq/ozP+q17oU+W8pGLugtR =XeW7 -----END PGP SIGNATURE-----
There is partclone - File System Clone Utilities Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-07-26 02:52, Roman Bysh wrote:
On 25/07/17 08:45 PM, Carlos E. R. wrote:
There is
partclone - File System Clone Utilities
He tried, but apparently the result had zero bytes. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF0EAREIAAYFAll364gACgkQja8UbcUWM1x4WwD/e25IObd/WUQvDdOD2Ysw7SOc iQYXvP/46Znd0NNCz9sA+IvIqufWTqZxNO8Ck/1uxWC+X6TxNEGoxgMbkYDbnMc= =u0Sm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, On Jul 25 20:57 Michael Hamilton wrote (excerpt):
In case it helps, I have written up notes on the structure of an openSUSE btrfs root volume and a bit about recreating a root volume:
https://forums.opensuse.org/showthread.php/521277-LEAP-42-2-btrfs-root-files...
Wow! A very good technical summary. As an addedum about how complicate it is to create an additional btrfs subvolume in compliance with our default btrfs subvolume structure, you may have a look at my (meanwhile probably already somewhat outdated) selfmade personal quick and dirty script in https://lists.opensuse.org/opensuse-factory/2016-10/msg00397.html
As well as the first post, there is a second post further down the thread concerning preserving copy-on-write attributes.
And don't forget btrfs quota setup for snapper that is used by default at least since SLE12-SP2. I don't know what Leap inherits from SLE12 service packs. As far as I know the "intelligence" how to setup the default btrfs subvolume structure and related things is built-in into the YaST installer (I mean the part of YaST plus helper tools like /usr/lib/snapper/installation-helper that run within the SUSE installation system "inst-sys") so that I assume it depends on what YaST installer version is used in Leap (and additionally it may depend on whatever product specific presets for the YaST installer). For each SLE12 service pack (at least up to SLE12-SP2) there was another (incompatible) change or another addon in the SUSE default btrfs subvolume setup that leads to "interesting effects" when using existing system recovery procedures. I.e. each SLE12 service pack needs a bit different recovery procedure when the default btrfs subvolume setup is used, cf. https://github.com/rear/rear/issues/1368#issuecomment-302410707 FYI for general background information about "ReaR", see "Disaster recovery with Relax-and-Recover (ReaR)" at https://en.opensuse.org/SDB:Disaster_Recovery Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-07-25 9:54 GMT-03:00 Johannes Meixner <jsmeix@suse.de>:
Hello,
On Jul 25 20:57 Michael Hamilton wrote (excerpt):
In case it helps, I have written up notes on the structure of an openSUSE btrfs root volume and a bit about recreating a root volume:
https://forums.opensuse.org/showthread.php/521277-LEAP-42-2-btrfs-root-files...
Wow! A very good technical summary.
As an addedum about how complicate it is to create an additional btrfs subvolume in compliance with our default btrfs subvolume structure, you may have a look at my (meanwhile probably already somewhat outdated) selfmade personal quick and dirty script in
https://lists.opensuse.org/opensuse-factory/2016-10/msg00397.html
As well as the first post, there is a second post further down the thread concerning preserving copy-on-write attributes.
And don't forget btrfs quota setup for snapper that is used by default at least since SLE12-SP2.
I don't know what Leap inherits from SLE12 service packs. As far as I know the "intelligence" how to setup the default btrfs subvolume structure and related things is built-in into the YaST installer (I mean the part of YaST plus helper tools like /usr/lib/snapper/installation-helper that run within the SUSE installation system "inst-sys") so that I assume it depends on what YaST installer version is used in Leap (and additionally it may depend on whatever product specific presets for the YaST installer).
For each SLE12 service pack (at least up to SLE12-SP2) there was another (incompatible) change or another addon in the SUSE default btrfs subvolume setup that leads to "interesting effects" when using existing system recovery procedures.
I.e. each SLE12 service pack needs a bit different recovery procedure when the default btrfs subvolume setup is used, cf.
https://github.com/rear/rear/issues/1368#issuecomment-302410707
FYI for general background information about "ReaR", see "Disaster recovery with Relax-and-Recover (ReaR)" at https://en.opensuse.org/SDB:Disaster_Recovery
At the first look it appears interesting.....but.... https://en.opensuse.org/SDB:Disaster_Recovery#How_to_contribute_to_Relax-and... Disaster recovery with rear-SUSE / RecoveryImage (outdated) ....... Native disaster recovery with AutoYaST (deprecated) I mean this is time that the developers of Suse/Opensuse add a Yast module for clone, backup and restore system. Years ago the installer DVD had the option "System repair", but today have nothing. Regards, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-07-25 15:35, Juan Erbes wrote:
2017-07-25 9:54 GMT-03:00 Johannes Meixner <>:
And don't forget btrfs quota setup for snapper that is used by default at least since SLE12-SP2.
I don't know what Leap inherits from SLE12 service packs. As far as I know the "intelligence" how to setup the default btrfs subvolume structure and related things is built-in into the YaST installer (I mean the part of YaST plus helper tools like /usr/lib/snapper/installation-helper that run within the SUSE installation system "inst-sys") so that I assume it depends on what YaST installer version is used in Leap (and additionally it may depend on whatever product specific presets for the YaST installer).
For each SLE12 service pack (at least up to SLE12-SP2) there was another (incompatible) change or another addon in the SUSE default btrfs subvolume setup that leads to "interesting effects" when using existing system recovery procedures.
I.e. each SLE12 service pack needs a bit different recovery procedure when the default btrfs subvolume setup is used, cf.
https://github.com/rear/rear/issues/1368#issuecomment-302410707
FYI for general background information about "ReaR", see "Disaster recovery with Relax-and-Recover (ReaR)" at https://en.opensuse.org/SDB:Disaster_Recovery
...
I mean this is time that the developers of Suse/Opensuse add a Yast module for clone, backup and restore system.
Yes, YaST should at least have a method to fully initialize a btrfs system partition different from the current root partition. Perhaps inside the partitioning module.
Years ago the installer DVD had the option "System repair", but today have nothing.
If you mean the automatic repair module, yes, that one disappeared. But rescue mode should still be there. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAll3TbQACgkQja8UbcUWM1xYWgEAkuF5FD9r+qmfrae1SyzL+TLi GS1b55iEJZAV/rG2q7sA/RiN/fHHRP5DqKwJ+B+y3R+KdFqbPLfKX7oBZTzTWjgk =gF3O -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
so you and I are still present after richard's rant :) do you know who was banned? perhaps Brian White... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [07-25-17 10:46]:
so you and I are still present after richard's rant :)
uuups :( -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
so you and I are still present after richard's rant :)
do you know who was banned? perhaps Brian White...
Please note, that this was not Richard's rant, this was a unanimous board decision. And that there is no need to ridicule anything about it. No need to CC the list, that is. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-07-25 10:55 GMT-03:00 Carlos E. R. <robin.listas@telefonica.net>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2017-07-25 15:35, Juan Erbes wrote:
2017-07-25 9:54 GMT-03:00 Johannes Meixner <>:
And don't forget btrfs quota setup for snapper that is used by default at least since SLE12-SP2.
I don't know what Leap inherits from SLE12 service packs. As far as I know the "intelligence" how to setup the default btrfs subvolume structure and related things is built-in into the YaST installer (I mean the part of YaST plus helper tools like /usr/lib/snapper/installation-helper that run within the SUSE installation system "inst-sys") so that I assume it depends on what YaST installer version is used in Leap (and additionally it may depend on whatever product specific presets for the YaST installer).
For each SLE12 service pack (at least up to SLE12-SP2) there was another (incompatible) change or another addon in the SUSE default btrfs subvolume setup that leads to "interesting effects" when using existing system recovery procedures.
I.e. each SLE12 service pack needs a bit different recovery procedure when the default btrfs subvolume setup is used, cf.
https://github.com/rear/rear/issues/1368#issuecomment-302410707
FYI for general background information about "ReaR", see "Disaster recovery with Relax-and-Recover (ReaR)" at https://en.opensuse.org/SDB:Disaster_Recovery
...
I mean this is time that the developers of Suse/Opensuse add a Yast module for clone, backup and restore system.
Yes, YaST should at least have a method to fully initialize a btrfs system partition different from the current root partition. Perhaps inside the partitioning module.
Years ago the installer DVD had the option "System repair", but today have nothing.
If you mean the automatic repair module, yes, that one disappeared. But rescue mode should still be there.
The latest probe now with dd. 60 GB copied in 360 seconds at 179 MB/sec. According to: https://forums.opensuse.org/showthread.php/524746-Cloning-root-partition-to-... Will see what happens at reboot. Thanks! -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-07-25 17:24 GMT-03:00 Juan Erbes <jerbes@gmail.com>:
2017-07-25 10:55 GMT-03:00 Carlos E. R. <robin.listas@telefonica.net>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2017-07-25 15:35, Juan Erbes wrote:
2017-07-25 9:54 GMT-03:00 Johannes Meixner <>:
And don't forget btrfs quota setup for snapper that is used by default at least since SLE12-SP2.
I don't know what Leap inherits from SLE12 service packs. As far as I know the "intelligence" how to setup the default btrfs subvolume structure and related things is built-in into the YaST installer (I mean the part of YaST plus helper tools like /usr/lib/snapper/installation-helper that run within the SUSE installation system "inst-sys") so that I assume it depends on what YaST installer version is used in Leap (and additionally it may depend on whatever product specific presets for the YaST installer).
For each SLE12 service pack (at least up to SLE12-SP2) there was another (incompatible) change or another addon in the SUSE default btrfs subvolume setup that leads to "interesting effects" when using existing system recovery procedures.
I.e. each SLE12 service pack needs a bit different recovery procedure when the default btrfs subvolume setup is used, cf.
https://github.com/rear/rear/issues/1368#issuecomment-302410707
FYI for general background information about "ReaR", see "Disaster recovery with Relax-and-Recover (ReaR)" at https://en.opensuse.org/SDB:Disaster_Recovery
...
I mean this is time that the developers of Suse/Opensuse add a Yast module for clone, backup and restore system.
Yes, YaST should at least have a method to fully initialize a btrfs system partition different from the current root partition. Perhaps inside the partitioning module.
Years ago the installer DVD had the option "System repair", but today have nothing.
If you mean the automatic repair module, yes, that one disappeared. But rescue mode should still be there.
The latest probe now with dd.
60 GB copied in 360 seconds at 179 MB/sec.
According to:
https://forums.opensuse.org/showthread.php/524746-Cloning-root-partition-to-...
Will see what happens at reboot.
Well! After changing the UUID of the volumes with: btrfstune -u /dev/sdb2 Verified the subvolumens with: btrfs sub list -u /mnt (sdb2 mounted on it) Changed the UUID for the root partition, home and swap on /etc/fstab, /etc/defaults/grub and /boot/grub/grub.cfg Applying brute force with "dd", it worked! I'm using now Opensuse Leap 42.3 kernel-4.4.76-1-default Need to adjust little details, but it works! Regards, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 23/07/17 09:45 AM, Carlos E. R. wrote:
I recommend using "DownThemAll!", a Firefox plugin, to do the download in Windows. It will automatically verify and correct downloads errors.
+1 I often make use of that. However I don't use Windows. I do have a spare Linux box. When I need to download a DVD or similar I use cURL or Wget. Please do remember that along with each DVD there is a MD5 checksum. If you are concerned about corruption of the download you should make use of that to verify its correctness. -- Over the last few centuries, mathematicians have demonstrated a remarkable tendency to underestimate the cryptanalytic powers of blunt and heavy objects. -- Jamie Reid, CISSP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 23/07/17 08:01 AM, Juan Erbes wrote:
As on my computer the Leap partition 42.1 was broken,
Just curious. If the partition was broken then if a fdisk (or equivalent) issue. If the file system was broken, that's another matter. -- Even the Four Horsemen of Kidporn, Dope Dealers, Mafia and Terrorists don't worry me as much as totalitarian governments. It's been a long century, and we've had enough of them. -- Bruce Sterling -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-07-23 23:49 GMT-03:00 Anton Aylward <opensuse@antonaylward.com>:
On 23/07/17 08:01 AM, Juan Erbes wrote:
As on my computer the Leap partition 42.1 was broken,
Just curious.
If the partition was broken then if a fdisk (or equivalent) issue. If the file system was broken, that's another matter.
This hard disk is a little old, with more than 7 years, a Western Digital of 1.5 TB Green series. The /home is in anther hard disk, a Toshiba of 2 TB SATA 3 with a little more than 1 year. Is time to see with smartctl the status of the hard disk. Thanks, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/23/2017 02:01 PM, Juan Erbes wrote:
Because I had to reinstall Leap because crashed the hard drive and I had to replace it on the computar of a friend, as my internet connection is slow, I asked a friend to download and record the DVD of the last beta of Leap 42.3. But as the download of the iso my friend made it from windows, the dvd was corrupt, and some of the packages failed in the installation, just like the installation of grub.
I choose to install Leap 42.2, and upgrade with the leap 42.3 beta dvd, with the internet connection enabled, and most of the packages were installed from the repositories, but it took about 6 hours to upgrade.
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
Both partitions, source and destination has about the same size of about 60 GB (the destination 59.4 GB).
FSArchiver usually makes a great job cloning filesystems to partitions with different sizes. It claims to support btrfs with some limitations, check if those are acceptable for you: http://www.fsarchiver.org/ Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-07-24 12:20 GMT-03:00 Ancor Gonzalez Sosa <ancor@suse.de>:
On 07/23/2017 02:01 PM, Juan Erbes wrote:
Because I had to reinstall Leap because crashed the hard drive and I had to replace it on the computar of a friend, as my internet connection is slow, I asked a friend to download and record the DVD of the last beta of Leap 42.3. But as the download of the iso my friend made it from windows, the dvd was corrupt, and some of the packages failed in the installation, just like the installation of grub.
I choose to install Leap 42.2, and upgrade with the leap 42.3 beta dvd, with the internet connection enabled, and most of the packages were installed from the repositories, but it took about 6 hours to upgrade.
As on my computer the Leap partition 42.1 was broken, I want to clone Leap 42.3 from the other disk. On my pc I have installed Leap 42.2, so no hard disk needs to be mounted, both the source and the destination to clone Leap 42.3.
¿Which is the better way?
Both partitions, source and destination has about the same size of about 60 GB (the destination 59.4 GB).
FSArchiver usually makes a great job cloning filesystems to partitions with different sizes. It claims to support btrfs with some limitations, check if those are acceptable for you:
Thank You! I will try it. USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-07-24 17:20, Ancor Gonzalez Sosa wrote:
FSArchiver usually makes a great job cloning filesystems to partitions with different sizes. It claims to support btrfs with some limitations, check if those are acceptable for you:
It says: There are several limitations anyway: it cannot preserve filesystem attributes that are very specific. For instance, if you create a snapshot in a btrfs volume (the new-generation file system for linux), FSArchiver won’t know anything about that, and it will just backup the contents seen when you mount the partition. ... You can have more details about the _current status_ of that project. .. current status: fsarchiver 0.6.10 and more recent versions are considered stable, except the NTFS support which is experimental. The latest stable version is 0.8.x and it is the recommended version for all users. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
2017-07-24 16:03 GMT-03:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2017-07-24 17:20, Ancor Gonzalez Sosa wrote:
FSArchiver usually makes a great job cloning filesystems to partitions with different sizes. It claims to support btrfs with some limitations, check if those are acceptable for you:
It says:
There are several limitations anyway: it cannot preserve filesystem attributes that are very specific. For instance, if you create a snapshot in a btrfs volume (the new-generation file system for linux), FSArchiver won’t know anything about that, and it will just backup the contents seen when you mount the partition. ... You can have more details about the _current status_ of that project.
.. current status:
fsarchiver 0.6.10 and more recent versions are considered stable, except the NTFS support which is experimental. The latest stable version is 0.8.x and it is the recommended version for all users.
The 2 programs are in the repos. With partclone.btrfs: partclone.btrfs -c -s /dev/sdb2 -o r-backup The log was: Partclone v0.3.5a http://partclone.org Starting to clone device (/dev/sdb2) to image (r-backup) Reading Super Block btrfsclone.c: btrfs library version = Btrfs v4.2.2 block_size = 16384 usedblock = 759835 device_size = 64428703744 totalblock = 3932416 btrfsclone.c: fs_close memory needed: 2588708 bytes bitmap 491552 bytes, blocks 2*1048576 bytes, checksum 4 bytes Calculating bitmap... Please wait... btrfsclone.c: btrfs library version = Btrfs v4.2.2 And the image generated has 0 bytes. With fsarchiver: fsarchiver savefs r-backup.fsa /dev/sdb2 Statistics for filesystem 0 * files successfully processed:....regfiles=184833, directories=16206, symlinks=21491, hardlinks=8811, specials=0 * files with errors:...............regfiles=0, directories=0, symlinks=0, hardlinks=0, specials=0 The generated file has: 2585637456 jul 24 17:25 r-backup.fsa The info of the file: fsarchiver archinfo r-backup.fsa ====================== archive information ====================== Archive type: filesystems Filesystems count: 1 Archive id: 5977577e Archive file format: FsArCh_002 Archive created with: 0.6.21 Archive creation date: 2017-07-24_17-18-36 Archive label: <none> Minimum fsarchiver version: 0.6.4.0 Compression level: 3 (gzip level 6) Encryption algorithm: none ===================== filesystem information ==================== Filesystem id in archive: 0 Filesystem format: btrfs Filesystem label: Filesystem uuid: ecb07b1b-4482-436c-a7d7-1b9220ebd14d Original device: /dev/sdb2 Original filesystem size: 60.00 GB (64428703744 bytes) Space used in filesystem: 12.23 GB (13128470528 bytes) Later I will see waht happens when I write to the new hard disk the FS. Regards, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-07-24 22:32, Juan Erbes wrote:
2017-07-24 16:03 GMT-03:00 Carlos E. R. <>:
On 2017-07-24 17:20, Ancor Gonzalez Sosa wrote:
The 2 programs are in the repos.
With partclone.btrfs:
partclone.btrfs -c -s /dev/sdb2 -o r-backup
The log was:
...
Calculating bitmap... Please wait...
btrfsclone.c: btrfs library version = Btrfs v4.2.2
And the image generated has 0 bytes.
Oh? :-(
With fsarchiver:
...
Later I will see waht happens when I write to the new hard disk the FS.
It is very imporant that you verify that all the volumes and subvolumes have been created. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
2017-07-24 17:36 GMT-03:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2017-07-24 22:32, Juan Erbes wrote:
2017-07-24 16:03 GMT-03:00 Carlos E. R. <>:
On 2017-07-24 17:20, Ancor Gonzalez Sosa wrote:
The 2 programs are in the repos.
With partclone.btrfs:
partclone.btrfs -c -s /dev/sdb2 -o r-backup
The log was:
...
Calculating bitmap... Please wait...
btrfsclone.c: btrfs library version = Btrfs v4.2.2
And the image generated has 0 bytes.
Oh? :-(
With fsarchiver:
...
Later I will see waht happens when I write to the new hard disk the FS.
It is very imporant that you verify that all the volumes and subvolumes have been created.
With fsarchiver worked fine, but the problem are the uuid from fstab: First make a check: btrfs check /dev/sdb2 Checking filesystem on /dev/sdb2 UUID: 8d6cdbd7-5b48-4243-92db-e23c0c361994 checking extents checking free space cache checking fs roots checking csums checking root refs found 6300626944 bytes used err is 0 total csum bytes: 5941084 total tree bytes: 215121920 total fs tree bytes: 197820416 total extent tree bytes: 9912320 btree space waste bytes: 31933990 file data blocks allocated: 6085505024 referenced 6085505024 Then changing the uuid: btrfstune -u /dev/sdb2 Warning: It's highly recommended to run 'btrfs check' before this operation Also canceling running UUID change progress may cause corruption We are going to change UUID, are your sure? [y/N]: y Current fsid: 8d6cdbd7-5b48-4243-92db-e23c0c361994 New fsid: 49be1afb-b010-4dff-9ed5-fd97b09bae52 Set superblock flag CHANGING_FSID Change fsid in extents Change fsid on devices Clear superblock flag CHANGING_FSID Fsid change finished After this, change the uuid in fstab, line by line. Now will see what happens after restart. -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (11)
-
Ancor Gonzalez Sosa -
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
Johannes Meixner -
Juan Erbes -
Knurpht - Gertjan Lettink -
Michael Hamilton -
Patrick Shanahan -
Richard Brown -
Roman Bysh