Attachment 14478 Details for Bug 47644 – fstransform log (un-def p10 hw)

fstransform log (un-def p10 hw)

fstransform-un-def-p10-hw.log (text/x-log), 4.41 KB, created by Artem Varaksa on 2023-09-19 17:59:55 MSK

(hide)

Description:

Filename:

MIME Type:

Creator: Artem Varaksa

Created: 2023-09-19 17:59:55 MSK

Size: 4.41 KB

patch

obsolete

>2023-09-19 15:39:36 fstransform: saving output of this execution into /var/tmp/fstransform/fstransform.log.11789
>2023-09-19 15:39:36 fstransform: preparing to transform device '/dev/sda4' to file-system type 'reiserfs'
>2023-09-19 15:39:36 fstransform: device is mounted at '/test-mount' with file-system type 'ext2'
>2023-09-19 15:39:36 fstransform: device raw size = 6524239872 bytes
>2023-09-19 15:39:36 fstransform: creating sparse loop file '/test-mount/.fstransform.loop.11789' inside device '/dev/sda4'...
>2023-09-19 15:39:36 dd: 1+0 Ð·Ð°Ð¿Ð¸ÑÐµÐ¹ Ð¿Ð¾Ð»ÑÑÐµÐ½Ð¾
>2023-09-19 15:39:36 dd: 1+0 Ð·Ð°Ð¿Ð¸ÑÐµÐ¹ Ð¾ÑÐ¿ÑÐ°Ð²Ð»ÐµÐ½Ð¾
>2023-09-19 15:39:36 dd: 1 Ð±Ð°Ð¹Ñ ÑÐºÐ¾Ð¿Ð¸ÑÐ¾Ð²Ð°Ð½, 0,000125403 s, 8,0 kB/s
>2023-09-19 15:39:36 fstransform: device file-system block size = 4096 bytes
>2023-09-19 15:39:36 fstransform: device usable size = 6524239872 bytes
>2023-09-19 15:39:36 dd: 1+0 Ð·Ð°Ð¿Ð¸ÑÐµÐ¹ Ð¿Ð¾Ð»ÑÑÐµÐ½Ð¾
>2023-09-19 15:39:36 dd: 1+0 Ð·Ð°Ð¿Ð¸ÑÐµÐ¹ Ð¾ÑÐ¿ÑÐ°Ð²Ð»ÐµÐ½Ð¾
>2023-09-19 15:39:36 dd: 1 Ð±Ð°Ð¹Ñ ÑÐºÐ¾Ð¿Ð¸ÑÐ¾Ð²Ð°Ð½, 8,5025e-05 s, 11,8 kB/s
>2023-09-19 15:39:36 fstransform: unmounting device '/dev/sda4' and remounting it read-only using kernel driver
>2023-09-19 15:39:36 fstransform: launching '/usr/sbin/fsremap' in simulated mode for pre-validation
>2023-09-19 15:39:36 fsremap: setting log level to NOTICE
>2023-09-19 15:39:36 fsremap: starting job 54, persistence data and logs are in '/var/tmp/fstransform/fsremap.job.54'
>2023-09-19 15:39:36 fsremap: analysis completed: 8.00 kilobytes must be relocated
>2023-09-19 15:39:36 fsremap: allocated 8.00 kilobytes RAM as memory buffer
>2023-09-19 15:39:36 fsremap: primary-storage is 1.00 megabytes, initialized and mmapped() to contiguous RAM
>2023-09-19 15:39:36 fsremap: (simulated) starting in-place remapping. this may take a LONG time ...
>2023-09-19 15:39:36 fsremap: (simulated) progress: 50.0% done,   8.0 kilobytes still to remap
>2023-09-19 15:39:36 fsremap: (simulated) clearing 6.08 gigabytes free-space from device ...
>2023-09-19 15:39:36 fsremap: (simulated) job completed.
>2023-09-19 15:39:36 fstransform: unmounting device '/dev/sda4' and remounting it read-write
>2023-09-19 15:39:36 fstransform: connected loop device '/dev/loop0' to file '/test-mount/.fstransform.loop.11789'
>2023-09-19 15:39:36 fstransform: formatting loop device '/dev/loop0' with file-system type 'reiserfs'...
>2023-09-19 15:39:36 mkfs: mkfs.reiserfs 3.6.27
>2023-09-19 15:39:36 mkfs:
>2023-09-19 15:39:36 fstransform: mounting loop device '/dev/loop0' on '/tmp/fstransform.loop.11789' ...
>2023-09-19 15:39:36 fstransform: loop device '/dev/loop0' mounted successfully.
>2023-09-19 15:39:36 fstransform: preliminary steps completed, now comes the delicate part:
>2023-09-19 15:39:36 fstransform: fstransform will move '/dev/sda4' contents into the loop file.
>
>2023-09-19 15:39:36 fstransform: WARNING: THIS IS IMPORTANT! if either the original device '/dev/sda4'
>                                or the loop device '/dev/loop0' become FULL,
>
>                                 YOU  WILL  LOSE  YOUR  DATA !
>
>                                fstransform checks for enough available space,
>                                in any case it is recommended to open another terminal, type
>                                  watch df /dev/sda4 /dev/loop0
>                                and check that both the original device '/dev/sda4'
>                                and the loop device '/dev/loop0' are NOT becoming full.
>                                if one of them is becoming full (or both),
>                                you MUST stop fstransform with CTRL+C or equivalent.
>
>2023-09-19 15:39:36 fstransform: moving '/dev/sda4' contents into the loop file.
>2023-09-19 15:39:36 fstransform: this may take a long time, please be patient...
>[...]
>
>2023-09-19 15:39:38 ERROR! fstransform: command '/usr/sbin/fsmove -- /test-mount /tmp/fstransform.loop.11789 --exclude /test-mount/.fstransform.loop.11789' failed (exit status 139)
>                          this is potentially a problem.
>                          you can either quit now by pressing ENTER or CTRL+C,
>
>                          or, if you know what went wrong, you can fix it yourself,
>                          then manually run the command '/usr/sbin/fsmove -- /test-mount /tmp/fstransform.loop.11789 --exclude /test-mount/.fstransform.loop.11789'
>                          (or something equivalent)
>                          and finally resume this script by typing CONTINUE and pressing ENTER:

Actions: View

Attachments on bug 47644: 14474 | 14476 | 14477 | 14478 | 14479