similar to: Best practice preparing for disk restoring system

Maybe "rear" is an appropriate solution for you? https://relax-and-recover.org/ On 17/11/2020 18:23, Chris Schanzle via CentOS wrote: > I would include LVM and mdadm info as well, since I use those features.? I encourage you to look at what long-lived tools, such as clonezilla, write into their archive directories.? It's impressive. > > If you zero out all free space on

I would include LVM and mdadm info as well, since I use those features.? I encourage you to look at what long-lived tools, such as clonezilla, write into their archive directories.? It's impressive. If you zero out all free space on all of your HDD partitions (dd bs=1M if=/dev/zero of=/path/deleteme; rm /path/deleteme) or use 'fstrim' for SSD's, you could use dd to image with fast

On November 17, 2020 4:07:52 PM EST, "Felix K?lzow" <felix.koelzow at gmx.de> wrote: >Maybe "rear" is an appropriate solution for you? > >https://relax-and-recover.org/ > >On 17/11/2020 18:23, Chris Schanzle via CentOS wrote: >> I would include LVM and mdadm info as well, since I use those >features.? I encourage you to look at what long-lived

On 18/11/2020 03:35, H wrote: > On November 17, 2020 4:07:52 PM EST, "Felix K?lzow" <felix.koelzow at gmx.de> wrote: >> Maybe "rear" is an appropriate solution for you? >> >> https://relax-and-recover.org/ >> >> On 17/11/2020 18:23, Chris Schanzle via CentOS wrote: >>> I would include LVM and mdadm info as well, since I use those

I still get the "the discard operation is not supported" fstrim error when the LVs are set to "nopassdown" Seems that when I use ext4 the fstrim reports that it worked but the LVs Data% does not decrease after the fstrim. xfs just throws the error. I've also been looking at the output of lsblk -D # lsblk -D NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO xvdb

Hi All I'm trying to setup my LVM thin pool to support discards so that the pool can reclaim space even if the underlying device doesn't support trim. It is my understanding that all thin pools should support trim even if the underlying device doesn't. (please correct me if I'm wrong here) I have one centos server that does support trim and everything is working correctly but any

The following patch attempts to implement sparsification of LUKS-encrypted partitions. It uses lsblk to pair the underlying LUKS block device with its mapped name. Also, --allow-discards was added by default to luks_open(). There are several potential issues that I can think of: 1) If and entire device is encrypted (not just one of more partitions), the lsblk trick might not work. 2) The

On Thu, May 28, 2020 19:38, Robert Nichols wrote: > What output do you get from: > > file -s /dev/mapper/vg_voinet01-lv_log > lsblk -f /dev/mapper/vg_voinet01-lv_log > file -s /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5' dm-f lsblk -f /dev/mapper/vg_voinet01-lv_log NAME FSTYPE LABEL UUID

I would like to have a smart cli tool, that shows a comprehensive list about the local storage structure: An output like: /srv /dev/mapper/luks-f85b7a2c-...: UUID="ca924fad-..." TYPE="ext4" /dev/mapper/vg_internal_e-lv_internal_srv: UUID="f85b7a2c-..." TYPE="crypto_LUKS" vg_internal_e /dev/md3: UUID="1Fi2Ex-..."

I'm old school, but I always liked using dump/restore on unix file systems. e2dump or whatever for linux, zfs send/recieve for zfs, ufsdump on freebsd ufs, etc etc. then I just need to know what file systems they are, and where they should be mounted, and its trivial to set tha tup on new hardware.

> What I've done in the past is before the nightly backup write a small > file to the root of each filesystem giving disk geometries.? You can > then use any recovery DVD to partition and reload the OS.? If rear can > do this for me it would be __much__ neater! According to rear webpage: https://relax-and-recover.org/about/ Extensive disk layout implementation, incl. * HWRAID

I'd agree with you John. I'm trying to get away from Amanda's unpredictability and go back to using scripts to drive dump (for ext2/3/4) and xfsdump (for xfs). Is there any easy way to tell rear to include xfsdump and dump capability? If the commands are there then its trivial to restore data. What I've done in the past is before the nightly backup write a small file to the

From: Jan Synacek <jan.synacek@redhat.com> --- daemon/listfs.ml | 19 ++++++++++++++++--- daemon/luks.c | 9 +++++---- generator/actions_core.ml | 3 ++- gobject/Makefile.inc | 2 ++ inspector/inspector.c | 2 +- sparsify/in_place.ml | 2 +- 6 files changed, 27 insertions(+), 10 deletions(-) diff --git a/daemon/listfs.ml b/daemon/listfs.ml index

Hi helpeRs, I have inherited a set of data files that use the file system as a sort of poor man's database, i.e., the data files are nested in directories that indicate which city they come from. For example: dir.create("deleteme") for(i in paste("deleteme", c("New York", "Los Angeles"), sep="/")) { dir.create(i) for(j in

CentOS-5.7 using fuse-ntfs-3g I have a HDD from a laptop that is being returned for repair replacement. I wish to remove certain files before sending the laptop back with the HDD. I have mouunted the HDD on my desktop as an ntfs filesystem using an external SATA / USB adapter. As root I then used the gnome desktop to move the desired files to trash. Now I wish to delete the contents of the

If there were a ?zfs send? datastream saved someplace, is there a way to verify the integrity of that datastream without doing a ?zfs receive? and occupying all that disk space? I am aware that ?zfs send? is not a backup solution, due to vulnerability of even a single bit error, and lack of granularity, and other reasons. However ... There is an attraction to ?zfs send? as an augmentation to the

Hi Rich and Pino, Commenting after a test. I've installed a RHEL 7 virtual machine with 2 disks, using the graphical installer. During the installation, I selected the 2 disks as well as encryption checkbox. It asked me for only one password. After the installation, when the machine boots, it asks for the password (showing a device UUID) only once. When connected as root, I can see that there

I converted an ext4 filesystem with btrfs-convert, mounted it, and wanted to do "lzop -d ...". The result was an immediate Oops (btrfs is on LVM, on dm-crypt, on /dev/sdb which is USB-connected). mini-904.img.lzo dentry_open failed BUG: unable to handle kernel paging request at ffffffcd IP: [<c01b5f36>] fput+0x6/0x30 *pde = 00575067 *pte = 00000000 Oops: 0002 [#1] SMP last sysfs

--- mltools/tools_utils-c.c | 8 ++++---- mltools/tools_utils.ml | 6 +++--- mltools/tools_utils.mli | 8 ++++++-- options/decrypt.c | 5 +++-- options/inspect.c | 2 +- options/options.h | 2 +- 6 files changed, 18 insertions(+), 13 deletions(-) diff --git a/mltools/tools_utils-c.c b/mltools/tools_utils-c.c index 6c43b8d..1dcebc4 100644 --- a/mltools/tools_utils-c.c +++

Replace GUESTFSD_EXT_CMD with a command line option ‘./guestfsd --print-external-commands’