Linux, photography and science.
ZFS on Linux has no support for creating pools with missing vdevs. Thats a benefit of mdadm which accepts a missing keyword in a list of devices.
But there is a workaround:
First, check the size of an existing device (all devices must have same size). In my case, each disk has 2000398934016 bytes. I’ve used fdisk to check the size but you can use whatever you want.
Now create parse file(s) with the given size.
Using an additional SSD disk as a second level cache for ARC - called L2ARC - can speed up your ZFS pool. But if you analyze how often the cache is used you find a very low hit ratio. To understand why the hit ratio is low you should know how the L2ARC works.
ZFS uses a primary cache - the ARC - which takes some space of your available RAM. Until the ARC is really full, no noteworthy data is written to the L2ARC. Thus, until the ARC cache is warm, the L2ARC cache isn’t used. But even it is not used, a read request triggers a lookup in ARC and then in L2ARC. Because both caches are cold after a reboot, you can see a lot of cache misses.
Starting wie Samba 4.4.0, it comes with multi-channel support as a new experimental feature. This is still marked as unstable in current 4.5.0 release, but if you’re crazy, you can enable it easily with a new smb.conf parameter.
Microsoft has introduced a new feature called SMB multi-channel into SMB 3.0 (available since Windows Server 2012). With multi-channel, you can share a SMB connection across multiple NICs to increase throughput and implementing fault-tolerant connections.
The Asrock C2750D4I and C2550D4I boards provides multiple 4-pin PWM connectors. PWM configuration is available in the BIOS hardware monitoring
section, but you can not change any parameters through the hwmon interface in /sys/class/hwmon. Asrock uses a Nuvoton chip (nct6776 compatible) for monitoring
hardware sensors but the fans are not connected to this chip. Instead, they are handled by the onboard BMC.
You can get the current state of the sensors with impi-sensors:
At first, we run a read-only badblocks scan on the device to find the corrupt blocks.
% badblocks /dev/sda
55575184
55575185
55575186
55575187
55575188
55575189
55575190
55575191
55575192
55575193
55575194
55575195
55575196
55575197
55575198
55575199
Now we know that block 55575184 - 55575199 are dead. If there are only a few blocks, it’s possible to replace these.
Change the interface name in /etc/udev/rules.d/75-persistent-net-generator.rules
ip link set eth1 down
ip link set eth1 name wan0
ip link set wan0 up
I want to extend a running KVM Linux guest system with a physical hard drive. I’ve connected the new disk via
virsh attach-disk my_vm /dev/sdf vdc
to connect sdf to vdc, but inside the guest, nothing happens.
The solution is simple: attaching a new disk requires a new virtio block controller which is a PCI device. The trick is to rescan the PCI bus system to detect the new controller:
echo 1 > /sys/bus/pci/rescan
Now lspci shows the new controller and dmesg shows the new vdc block device.
00:08.0 SCSI storage controller: Red Hat, Inc Virtio block device
Simply load the both modules
acpiphp pci_hotplug
then you don’t need to rescan the PCI bus.