-
-
Notifications
You must be signed in to change notification settings - Fork 268
Closed
Labels
Milestone
Description
rear master
During #882 (comment) I noticed messages on the screen
that are not logged in the rear log file.
I did "rear -d -D recover" and got this on the screen
(excerpts - long lines wrapped):
RESCUE g130:~ # rear -d -D recover
...
Creating filesystem of type btrfs with mount point / on /dev/sda3.
8 bytes [5f 42 48 52 66 53 5f 4d] erased at offset 0x10040 (btrfs)
Btrfs v3.18.2+
ATTENTION:
mkfs.btrfs is not intended to be used directly. Please use the
YaST partitioner to create and manage btrfs filesystems to be
in a supported state on SUSE Linux Enterprise systems.
Performing full device TRIM (18.38GiB) ...
Turning ON incompat feature 'extref': increased hardlink limit
per file to 65536
fs created label (null) on /dev/sda3
nodesize 4096 leafsize 4096 sectorsize 4096 size 18.38GiB
Mounting filesystem /
But in /var/log/rear/rear-g130.log (in the running recovery system)
there is only (excerpt - long lines wrapped):
+++ LogPrint 'Creating filesystem of type btrfs with mount point / on /dev/sda3.' +++ Log 'Creating filesystem of type btrfs with mount point / on /dev/sda3.' +++ test 1 -gt 0 ++++ Stamp ++++ date '+%Y-%m-%d %H:%M:%S.%N ' +++ echo '2016-06-17 14:42:24.248377595 Creating filesystem of type btrfs with mount point / on /dev/sda3.' 2016-06-17 14:42:24.248377595 Creating filesystem of type btrfs with mount point / on /dev/sda3. +++ Print 'Creating filesystem of type btrfs with mount point / on /dev/sda3.' +++ test -n 1 +++ echo -e 'Creating filesystem of type btrfs with mount point / on /dev/sda3.' +++ mount +++ grep -q /dev/sda3 +++ wipefs -a /dev/sda3 +++ grep -q /dev/sda3 +++ mount +++ mkfs -t btrfs -f /dev/sda3 ++++ grep -o 'uuid: .*' ++++ cut -d : -f 2 ++++ tr -d '[:space:]' ++++ btrfs filesystem show /dev/sda3 +++ new_uuid=56e33393-d7aa-4750-8a41-67a5e8b12fda +++ '[' ffa23495-df2a-4a08-9233-4b84faea5d40 '!=' 56e33393-d7aa-4750-8a41-67a5e8b12fda ']' +++ grep -q ffa23495-df2a-4a08-9233-4b84faea5d40 /var/lib/rear/layout/fs_uuid_mapping grep: /var/lib/rear/layout/fs_uuid_mapping: No such file or directory +++ echo 'ffa23495-df2a-4a08-9233-4b84faea5d40 56e33393-d7aa-4750-8a41-67a5e8b12fda /dev/sda3' +++ LogPrint 'Mounting filesystem /' +++ Log 'Mounting filesystem /' +++ test 1 -gt 0 ++++ Stamp ++++ date '+%Y-%m-%d %H:%M:%S.%N ' +++ echo '2016-06-17 14:42:24.390821545 Mounting filesystem /' 2016-06-17 14:42:24.390821545 Mounting filesystem / +++ Print 'Mounting filesystem /' +++ test -n 1 +++ echo -e 'Mounting filesystem /'
I.e. nothing at all in the log about
Btrfs v3.18.2+
ATTENTION:
mkfs.btrfs is not intended to be used directly. Please use the
YaST partitioner to create and manage btrfs filesystems to be
in a supported state on SUSE Linux Enterprise systems.
Performing full device TRIM (18.38GiB) ...
Turning ON incompat feature 'extref': increased hardlink limit
per file to 65536
fs created label (null) on /dev/sda3
nodesize 4096 leafsize 4096 sectorsize 4096 size 18.38GiB
Perhaps this is a general missing functionality in rear
that everything what appears on the screen is also logged?
@gdha
do you know if everything what appears on the screen
should also be logged when '-d' and '-D' is used
or do I do something wrong?