From 3839b5e390c53b74f58003cf082030df02391f9a Mon Sep 17 00:00:00 2001
From: johannst Set This may help to find which processes keep devices busy when trying to unmount
+and the device is currently busy.Example
+Example
+# Start gdbserver.
gdbserver localhost:1234 /bin/ls
# Attach gdb.
gdb -ex 'target remote localhost:1234'
Wrapper example: Set environment variables just for the debugee
+env
as execution wrapper with some variables.
+The wrapper will be executed before the debugee.gdbserver --wrapper env FOO=123 BAR=321 -- :12345 /bin/ls
+
radare2(1)
print
@@ -2396,6 +2408,12 @@ digraph {
IPv4 TCP connections in
ESTABLISHED
state
+lsof -i 4TCP -s TCP:ESTABLISHED
List open files in a mounted directory.
+# Assuming /proc is a mount point.
+lsof /proc
+
ss(8)
@@ -4978,6 +4996,8 @@ zpool status
active host and ss [option] [filter]
imported
on the new host.
# Export a pool called MOOSE.
zpool export moose
+# If datasets are busy, use lsof to check which processes keep it busy.
+# lsof <mntpoint>
# List pools that can be imported using BY-ID deivce names (for example).
zpool import -d /dev/disk/by-id
@@ -5014,11 +5034,12 @@ zfs unmount moose/foo
Encryption is a readonly property, can only be set when creating a dataset.
-# Create encrypted dataset ENC on pool MOOSE.
+# Create encrypted dataset FOO on pool MOOSE.
zfs create -o encryption=on -o keyformat=passphrase moose/foo
-# Mount encrypte dataset (if key is not loaded).
+# Mount encrypte dataset and load encryption key (if not loaded).
zfs mount -l moose/foo
+# -l is equivalent to first loading the key via zfs load-key moose/foo.
# Unmount dataset and unload encryption key (unload is optional).
zfs umount -u moose/foo
--
cgit v1.2.3