search for: diskb

...ted. The disks should be virtually identical but they do not seem to be. First, my mount command is this (I edited a bit for brevity) mount -t ntfs-3g -o locale=nl_NL.iso-8859-1,silent /dev/disk/by-id/usb-DiskA \ /mnt/tmp || mount -t ntfs-3g -o locale=nl_NL.iso-9959-1,silent /dev/disk/by-id/usb-DiskB \ /mnt/tmp || mount -t ntfs-3g -o locale=nl_NL.iso-9959-1,silent /dev/disk/by-id/usb-DiskC \ /mnt/tmp if [ $? -eq 0 ] then <backup starts> So, it first attempts to mount diskA; if that fails, it tries diskB, and so on. DiskA has been running for a week without any problems or messages. No...

Hi, Is it possible to convert a zfs pool from a concatenation of 2 disks to a 2 way mirror without backing up the data, re-creating the pool and restoring it. i.e diskA,diskB ----> mirror(diskA,diskB) Thanks, Jeff

Hello All, I''m transitioning data off my old UFS partitions onto ZFS. I don''t have a lot of duplicate space so I created a zpool, rsync''ed the data from UFS to the ZFS mount and then repartitioned the UFS drive to have partitions that match the cylinder count of the ZFS. The idea here is that once the data is over I wipe out UFS and then attach that partition to the

...hink this might be the answer, but I would like to be sure what the compromise is if I go down this path. I am trying to set up a file server for my home office. I would like as much storage space as possible, and I need to be able to survive one drive failing. Here is what I have: DiskA - 160GB DiskB - 200GB DiskC - 250GB DiskD - 500GB DiskE - 500GB (I also have a separate 20GB disk that I will be booting from.) Here is the best way I can see to maximize storage: -160GB slice on all disks --Put these into a raidz1 zpool -40GB slice on disks B through E --Put these into a raidz1 zpool -50GB sl...

As mentioned last night, we''ve been reviewing a proposal for hot spare support in ZFS. Below you can find a current draft of the proposed interfaces. This has not yet been submitted for ARC review, but comments are welcome. Note that this does not include any enhanced FMA diagnosis to determine when a device is "faulted". This will come in a follow-on project, of which some

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.