[opensuse] loop mount question.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, If I create a full disk image with dd, is it possible to access the single partitions in it? Perhaps attach a loop device to the image. But then, how do I get access to the partitions inside, separately? I don't have the image yet, I intend to do it later, while I sleep. But if it is not possible to access the partitions, then perhaps I should do it differently. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF0EAREIAAYFAlXwLHIACgkQja8UbcUWM1zKPQD/TAT2ZZW5yG0npAHGon2OugbY hMDf9bOManPv2os2+h0A+OXcGz3n727pHJYdI0r1NTgIqQ7rOaLtHGx4UOJSxNQ= =lYW1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/09/2015 02:56 PM, Carlos E. R. wrote:
Hi,
If I create a full disk image with dd, is it possible to access the single partitions in it?
Perhaps attach a loop device to the image. But then, how do I get access to the partitions inside, separately?
I don't have the image yet, I intend to do it later, while I sleep. But if it is not possible to access the partitions, then perhaps I should do it differently.
- -- Cheers Carlos E. R.
Hi Carlos ! Is it what you want ? : # dd if=/dev/zero of=/home/me/tmp/ex6/file.dat bs=1024 count=50000 50000+0 records in 50000+0 records out 51200000 bytes (51 MB) copied, 0.136642 s, 375 MB/s (create the file) # losetup -f /dev/loop0 (to know the next available loops) # losetup /dev/loopX /home/me/tmp/ex6/file.dat # fdisk /dev/loop0 (here create 2 partitions with fdisk...) LRAF-FGA1:~ # partprobe Here it seems I would need to reboot, which I can't know. Dsant, from France -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/09/2015 03:15 PM, Dsant wrote:
On 09/09/2015 02:56 PM, Carlos E. R. wrote:
If I create a full disk image with dd, is it possible to access the single partitions in it?
Perhaps attach a loop device to the image. But then, how do I get access to the partitions inside, separately?
I don't have the image yet, I intend to do it later, while I sleep. But if it is not possible to access the partitions, then perhaps I should do it differently.
- -- Cheers Carlos E. R.
Hi Carlos !
Is it what you want ? :
# dd if=/dev/zero of=/home/me/tmp/ex6/file.dat bs=1024 count=50000 50000+0 records in 50000+0 records out 51200000 bytes (51 MB) copied, 0.136642 s, 375 MB/s
(create the file)
# losetup -f /dev/loop0
(to know the next available loops)
# losetup /dev/loopX /home/me/tmp/ex6/file.dat
# fdisk /dev/loop0
(here create 2 partitions with fdisk...)
LRAF-FGA1:~ # partprobe
Here it seems I would need to reboot, which I can't know.
Dsant, from France
It works ! No need to reboot, use partprobe and... the new devices are in folder /dev/mapper/ mkfs.ext3 /dev/mapper/loop0p1 mount /dev/mapper/loop0p1 /mnt/loop/ Enjoy ! Dsant, from France -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-09 15:34, Dsant wrote:
It works ! No need to reboot, use partprobe and... the new devices are in folder /dev/mapper/
mkfs.ext3 /dev/mapper/loop0p1
mount /dev/mapper/loop0p1 /mnt/loop/
Enjoy !
Wow, thanks! That's exactly what I wanted, yes. Far easier than I thought would be. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXwN/cACgkQja8UbcUWM1yPZAD/eHMrD5f0BOoSjm+vKTvpPNHw 5m8xWy+9MCExJWy83hUA/32SIvVODEL2zmi50s3QuUZb5WBwhuOxo3ItMwjRWniX =hkES -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Отправлено с iPhone
9 сент. 2015 г., в 16:45, Carlos E. R. <robin.listas@telefonica.net> написал(а):
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-09-09 15:34, Dsant wrote:
It works ! No need to reboot, use partprobe and... the new devices are in folder /dev/mapper/
mkfs.ext3 /dev/mapper/loop0p1
mount /dev/mapper/loop0p1 /mnt/loop/
Enjoy !
Wow, thanks! That's exactly what I wanted, yes. Far easier than I thought would be.
losetup -P is even easier :)
- -- Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlXwN/cACgkQja8UbcUWM1yPZAD/eHMrD5f0BOoSjm+vKTvpPNHw 5m8xWy+9MCExJWy83hUA/32SIvVODEL2zmi50s3QuUZb5WBwhuOxo3ItMwjRWniX =hkES -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-09 15:49, Andrei Borzenkov wrote:
Wow, thanks! That's exactly what I wanted, yes. Far easier than I thought would be.
losetup -P is even easier :)
Indeed! I missed that when I read the manual. Or I missed the implication. Thanks :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXwO7UACgkQja8UbcUWM1zJ3AD/dFgEBetB7xFW48ugLGUXFVUA xFqshOTYkt4ZhZU0260A/1Y6fWupzqsoug1CggC7DTpyYJMDits0mxrjjxGridXq =AnDk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
If I create a full disk image with dd, is it possible to access the single partitions in it?
Perhaps attach a loop device to the image. But then, how do I get access to the partitions inside, separately?
I don't have the image yet, I intend to do it later, while I sleep. But if it is not possible to access the partitions, then perhaps I should do it differently.
I think you can do this with kpartx, but I don't remember how. -- Per Jessen, Zürich (19.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Sep 9, 2015 at 8:56 AM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi,
If I create a full disk image with dd, is it possible to access the single partitions in it?
Perhaps attach a loop device to the image. But then, how do I get access to the partitions inside, separately?
I don't have the image yet, I intend to do it later, while I sleep. But if it is not possible to access the partitions, then perhaps I should do it differently.
Carlos, First mmls is a good tool for dumping the partition table from dd images. Then, ignoring LVM type volumes, you just use the offset arg of mount. It hides some of the complexity. "mount -loop -o <offset_in_bytes> <dd.img> <mnt_point>" A couple examples pulled from the web: # mount -t vfat -o loop,offset=32256,ro,noexec img.dd /mnt/tmp_1 # mount -t vfat -o loop,offset=20974464000,ro,noexec img.dd /mnt/tmp_2 The only hard part is remember the MBR tracks partition start in sectors, so you have to convert that to bytes for the mount command. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-09 15:50, Greg Freemyer wrote:
Carlos,
First mmls is a good tool for dumping the partition table from dd images.
Then, ignoring LVM type volumes, you just use the offset arg of mount. It hides some of the complexity.
"mount -loop -o <offset_in_bytes> <dd.img> <mnt_point>"
Interesting! However, for my purpose, "losetup -P" seems much easier :-) No calculations needed, thus no possibility of error. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXwPjsACgkQja8UbcUWM1zN3wD/ZNOfl4WH0jkzo0dmpKDELcV6 je7bljKi9CYuB03iGmAA/0lVjXKnTM5KXz2jA9x0gS2rj8soJqfU7tK/gtBspXWu =UXN6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Sep 9, 2015 at 8:56 AM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi,
If I create a full disk image with dd, is it possible to access the single partitions in it?
Perhaps attach a loop device to the image. But then, how do I get access to the partitions inside, separately?
I don't have the image yet, I intend to do it later, while I sleep. But if it is not possible to access the partitions, then perhaps I should do it differently.
Carlos, This is for extra credit only: === Not responding directly to your question, but you know I make a lot of "dd-equivalent" disk images. I prefer to create EWF formatted images. They have embedded CRC checksums as well as an overall hash. You can verify their integrity without having to have an external hash file to compare against. ewfacquire is in the distro and will create EWF formatted images. It will also split them up into 2GB segment files (by default). image.E01, image.E02, .... You can use ewfverify to check the CRCs and hash verify the image as valid. When you want to access it as a linear dd image equivalent you use ewfmount. The only confusing part (for me) is if you want to do a partition mount, you have to do 2 mounts: ewfmount first exposes the EWF image as a single large virtual disk Then a nomal loop mount is needed to mount a specific partition. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-09 21:07, Greg Freemyer wrote:
Not responding directly to your question, but you know I make a lot of "dd-equivalent" disk images.
I prefer to create EWF formatted images. They have embedded CRC checksums as well as an overall hash. You can verify their integrity without having to have an external hash file to compare against.
Ah, that's interesting. I don't know if I need that much, though. I'll explain my purpose. I have a double boot laptop, windows 7 / Linux. Microsoft proposes that I update to Windows 10. Before doing that, I want to create an image backup that allows me to restore Linux, if destroyed, or W7, if I want to go back to it. Thus I want the image for a limited time only: I either continue using W10, or restore W7.
ewfacquire is in the distro and will create EWF formatted images. It will also split them up into 2GB segment files (by default). image.E01, image.E02, ....
You can use ewfverify to check the CRCs and hash verify the image as valid.
If not, does it store recovery data to repair it?
When you want to access it as a linear dd image equivalent you use ewfmount.
The only confusing part (for me) is if you want to do a partition mount, you have to do 2 mounts:
ewfmount first exposes the EWF image as a single large virtual disk
Then a nomal loop mount is needed to mount a specific partition.
I can try, I guess... I'm installing now libewf2 and libewf2-tools to try. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXwlakACgkQja8UbcUWM1z12AD8Cqoo76/Ifq9t5hcL0VgUHbUL lrBELsM104fPB6GLkwUA/iwWB9LTG3RKGWDpfndX3wlAqjxUTAxv3yUIoBdp6pUo =SeTn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Sep 9, 2015 at 4:25 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-09-09 21:07, Greg Freemyer wrote:
Not responding directly to your question, but you know I make a lot of "dd-equivalent" disk images.
I prefer to create EWF formatted images. They have embedded CRC checksums as well as an overall hash. You can verify their integrity without having to have an external hash file to compare against.
Ah, that's interesting. I don't know if I need that much, though. I'll explain my purpose.
I have a double boot laptop, windows 7 / Linux. Microsoft proposes that I update to Windows 10. Before doing that, I want to create an image backup that allows me to restore Linux, if destroyed, or W7, if I want to go back to it.
Thus I want the image for a limited time only: I either continue using W10, or restore W7.
I have found hardware issues can corrupt the original image more often than you would think. I made about 65 images in one week last summer, then I made copies of all of them. I used numerous customer provided PCs to do the work. I used ewfverify on all of them to make sure they were good. I don't recall exactly, but there were 4 or 5 I had to re-perform because the verify failed. Also, I ended up tossing one of my destination drives because the images it held were all flaky. But yes, even with random PCs 95% of the time it works as planned. And if you are using a trusted PC then the odds are much higher. PCs that corrupt images tend to have bad RAM or bad cables, but it can be any flaky item in the PC to cause a verify failure.
ewfacquire is in the distro and will create EWF formatted images. It will also split them up into 2GB segment files (by default). image.E01, image.E02, ....
You can use ewfverify to check the CRCs and hash verify the image as valid.
If not, does it store recovery data to repair it?
man ewfrecover I don't recall ever using it. I keep at least 2 copies of all images. If one of them fails to verify, I make another copy of the good one.
When you want to access it as a linear dd image equivalent you use ewfmount.
The only confusing part (for me) is if you want to do a partition mount, you have to do 2 mounts:
ewfmount first exposes the EWF image as a single large virtual disk
Then a nomal loop mount is needed to mount a specific partition.
I can try, I guess...
I'm installing now libewf2 and libewf2-tools to try.
As I said, this is going a little above and beyond, but they are my everyday tools. I need trustworthy images that I can depend on years later. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-09 22:25, Carlos E. R. wrote:
On 2015-09-09 21:07, Greg Freemyer wrote:
...
I can try, I guess...
I'm installing now libewf2 and libewf2-tools to try.
Awfully slow. :-( minas-tirith:/mnt/nfs_telcontar/data/aux_01/Minas-Tirith # time ewfacquire -l test.log -t testimage /dev/sda ewfacquire 20130416 Device information: Bus type: ATA/ATAPI Vendor: ATA Model: ST9500325AS Serial: ***** Storage media information: Type: Device Media type: Fixed Media size: 500 GB (500107862016 bytes) Bytes per sector: 512 Acquiry parameters required, please provide the necessary input Case number: 1 Description: testing ewf accquire Evidence number: Examiner name: CER Notes: Media type (fixed, removable, optical, memory) [fixed]: Media characteristics (logical, physical) [physical]: Use EWF file format (ewf, smart, ftk, encase1, encase2, encase3, encase4, encase5, encase6, linen5, linen6, ewfx) [encase6]: Compression method (deflate) [deflate]: Compression level (none, empty-block, fast, best) [none]: fast Start to acquire at offset (0 <= value <= 500107862016) [0]: The number of bytes to acquire (0 <= value <= 500107862016) [500107862016]: Evidence segment file size in bytes (1.0 MiB <= value <= 7.9 EiB) [1.4 GiB]: The number of bytes per sector (1 <= value <= 4294967295) [512]: The number of sectors to read at once (16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384, 32768) [64]: The number of sectors to be used as error granularity (1 <= value <= 64) [64]: The number of retries when a read error occurs (0 <= value <= 255) [2]: Wipe sectors on read error (mimic EnCase like behavior) (yes, no) [no]: The following acquiry parameters were provided: Image path and filename: testimage.E01 Case number: 1 Description: testing ewf accquire Evidence number: Evidence number: Examiner name: CER Notes: Media type: fixed disk Is physical: yes EWF file format: EnCase 6 (.E01) Compression method: deflate Compression level: fast Acquiry start offset: 0 Number of bytes to acquire: 465 GiB (500107862016 bytes) Evidence segment file size: 1.4 GiB (1572864000 bytes) Bytes per sector: 512 Block size: 64 sectors Error granularity: 64 sectors Retries on read error: 2 Zero sectors on read error: no Continue acquiry with these values (yes, no) [yes]: Acquiry started at: Wed Sep 9 23:39:57 2015 This could take a while. Status: at 0%. acquired 32 KiB (32768 bytes) of total 465 GiB (500107862016 bytes). Status: at 1%. acquired 4.6 GiB (5001084928 bytes) of total 465 GiB (500107862016 bytes). completion in 21 hour(s), 58 minute(s) and 21 second(s) with 5.9 MiB/s (6259172 bytes/second). The destination drive is an NFS mount, using gigabit cable network, so not the issue. I see the network being mostly iddle, then a burst of activity. CPU is mostly iddle on both machines, with bursts of 100% of one core at source machine, coupled with disk read activity. This is unusable. I think I will use one of the dd-rescue variants instead. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXwrXEACgkQja8UbcUWM1xEKwEAm9XjWtUcxnFGO9svQZucIqA+ CARXJ3mTWtPodXB+SRgBAINIDxvddEpU5sfIcEoTfyDWNbEWwScqgEmHKvmAISr5 =aG4c -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Sep 9, 2015 at 6:06 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-09-09 22:25, Carlos E. R. wrote:
On 2015-09-09 21:07, Greg Freemyer wrote:
...
I can try, I guess...
I'm installing now libewf2 and libewf2-tools to try.
Awfully slow. :-(
I don't recall ever seeing it run that slow. Must be something about your setup it doesn't like. I often use the "empty-block" compression to make it run faster, but that doesn't seem to be your problem. Sorry, Greg
minas-tirith:/mnt/nfs_telcontar/data/aux_01/Minas-Tirith # time ewfacquire -l test.log -t testimage /dev/sda ewfacquire 20130416
Device information: Bus type: ATA/ATAPI Vendor: ATA Model: ST9500325AS Serial: *****
Storage media information: Type: Device Media type: Fixed Media size: 500 GB (500107862016 bytes) Bytes per sector: 512
Acquiry parameters required, please provide the necessary input Case number: 1 Description: testing ewf accquire Evidence number: Examiner name: CER Notes: Media type (fixed, removable, optical, memory) [fixed]: Media characteristics (logical, physical) [physical]: Use EWF file format (ewf, smart, ftk, encase1, encase2, encase3, encase4, encase5, encase6, linen5, linen6, ewfx) [encase6]: Compression method (deflate) [deflate]: Compression level (none, empty-block, fast, best) [none]: fast Start to acquire at offset (0 <= value <= 500107862016) [0]: The number of bytes to acquire (0 <= value <= 500107862016) [500107862016]: Evidence segment file size in bytes (1.0 MiB <= value <= 7.9 EiB) [1.4 GiB]: The number of bytes per sector (1 <= value <= 4294967295) [512]: The number of sectors to read at once (16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384, 32768) [64]: The number of sectors to be used as error granularity (1 <= value <= 64) [64]: The number of retries when a read error occurs (0 <= value <= 255) [2]: Wipe sectors on read error (mimic EnCase like behavior) (yes, no) [no]:
The following acquiry parameters were provided: Image path and filename: testimage.E01 Case number: 1 Description: testing ewf accquire Evidence number: Evidence number: Examiner name: CER Notes: Media type: fixed disk Is physical: yes EWF file format: EnCase 6 (.E01) Compression method: deflate Compression level: fast Acquiry start offset: 0 Number of bytes to acquire: 465 GiB (500107862016 bytes) Evidence segment file size: 1.4 GiB (1572864000 bytes) Bytes per sector: 512 Block size: 64 sectors Error granularity: 64 sectors Retries on read error: 2 Zero sectors on read error: no
Continue acquiry with these values (yes, no) [yes]:
Acquiry started at: Wed Sep 9 23:39:57 2015
This could take a while.
Status: at 0%. acquired 32 KiB (32768 bytes) of total 465 GiB (500107862016 bytes).
Status: at 1%. acquired 4.6 GiB (5001084928 bytes) of total 465 GiB (500107862016 bytes). completion in 21 hour(s), 58 minute(s) and 21 second(s) with 5.9 MiB/s (6259172 bytes/second).
The destination drive is an NFS mount, using gigabit cable network, so not the issue. I see the network being mostly iddle, then a burst of activity. CPU is mostly iddle on both machines, with bursts of 100% of one core at source machine, coupled with disk read activity.
This is unusable. I think I will use one of the dd-rescue variants instead.
- -- Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlXwrXEACgkQja8UbcUWM1xEKwEAm9XjWtUcxnFGO9svQZucIqA+ CARXJ3mTWtPodXB+SRgBAINIDxvddEpU5sfIcEoTfyDWNbEWwScqgEmHKvmAISr5 =aG4c -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-10 00:06, Carlos E. R. wrote:
Status: at 1%. acquired 4.6 GiB (5001084928 bytes) of total 465 GiB (500107862016 bytes). completion in 21 hour(s), 58 minute(s) and 21 second(s) with 5.9 MiB/s (6259172 bytes/second).
Without compression it runs at double speed, but I doubt it is the fastest the hardware is capable. Status: at 2%. acquired 9.3 GiB (10002169856 bytes) of total 465 GiB (500107862016 bytes). completion in 11 hour(s), 41 minute(s) and 31 second(s) with 11 MiB/s (11643954 bytes/second). - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXws8UACgkQja8UbcUWM1xZ0QD/Q8AyoTSNv1ZCq3m1i7PTo9dX LFlCRR8d5ZtI/LkVmucA/1pc5Ybb3aYFCIYYn/NBU8Swsdhi/E0weu1mB0t6ZWcQ =HyF7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Sep 9, 2015 at 6:33 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-09-10 00:06, Carlos E. R. wrote:
Status: at 1%. acquired 4.6 GiB (5001084928 bytes) of total 465 GiB (500107862016 bytes). completion in 21 hour(s), 58 minute(s) and 21 second(s) with 5.9 MiB/s (6259172 bytes/second).
Without compression it runs at double speed, but I doubt it is the fastest the hardware is capable.
Status: at 2%. acquired 9.3 GiB (10002169856 bytes) of total 465 GiB (500107862016 bytes). completion in 11 hour(s), 41 minute(s) and 31 second(s) with 11 MiB/s (11643954 bytes/second).
As you said, I'd try other solutions. If they too are slow, then troubleshooting may be worth the effort. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/10/2015 12:54 AM, Greg Freemyer wrote:
On Wed, Sep 9, 2015 at 6:33 PM, Carlos E. R. <> wrote:
As you said, I'd try other solutions.
If they too are slow, then troubleshooting may be worth the effort.
I found out why. The laptop network is not gigabit; the desktop is. So that 11 MiB/s is about the maximum. I would then get faster speed writing to a USB2 disk (480 Mbit/s is more than 100 Mbit/s). But as it will run most of the time while I sleep, it doesn't matter much. However, I don't understand why it runs at only 5.9MiB/s with "fast" compression enabled. The idea was to compress the data so that the network needs to transmit less bytes, and thus, at the same network speed, it would store faster. But I fear the compression algorithm used by this program is not implemented for speed; it does not run full time, judging by the intermittent CPU load. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On September 9, 2015 9:57:51 PM EDT, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 09/10/2015 12:54 AM, Greg Freemyer wrote:
On Wed, Sep 9, 2015 at 6:33 PM, Carlos E. R. <> wrote:
As you said, I'd try other solutions.
If they too are slow, then troubleshooting may be worth the effort.
I found out why. The laptop network is not gigabit; the desktop is. So that 11 MiB/s is about the maximum.
I would then get faster speed writing to a USB2 disk (480 Mbit/s is more than 100 Mbit/s). But as it will run most of the time while I sleep, it doesn't matter much.
However, I don't understand why it runs at only 5.9MiB/s with "fast" compression enabled. The idea was to compress the data so that the network needs to transmit less bytes, and thus, at the same network speed, it would store faster.
But I fear the compression algorithm used by this program is not implemented for speed; it does not run full time, judging by the intermittent CPU load.
I can only say I find the compression algorithm slow so I typically just do empty-block compression. Greg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/10/2015 05:06 AM, greg.freemyer@gmail.com wrote:
I can only say I find the compression algorithm slow so I typically just do empty-block compression.
Yes. But this was unexpected. I also noticed that the machine becomes very unresponsive while this runs (it is still running, 1 hour left). So I'm doing this periodically: linux:~ # free -h && echo && sync && \ echo 1 > /proc/sys/vm/drop_caches && free -h && echo "========" This way I can still use the laptop while it creates the image (running XFCE rescue image off an USB stick) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E. R. -
Dsant -
Greg Freemyer -
greg.freemyer＠gmail.com
-
Per Jessen