Jaculabilis/www
1
0
Fork 0
Code

CSS updates

Browse Source
This commit is contained in:
Tim Van Baak 2025-03-05 07:39:40 -08:00
parent 4b64376e7d
commit 1ca36a0b2c
2 changed files with 10 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/.template.html
View File

@ -53,9 +53,10 @@ sup {
background: palegoldenrod;
}
pre {
background: lightgray;
background: rgb(232,232,232);
padding: 5px;
line-height: initial;
white-space: pre-wrap;
}
</style>
</head>
@ -68,4 +69,4 @@ pre {
<article>This content is replaced.</article>
</main>
</body>
</html>
</html>

26
src/post/2023/zfs-nas-backup.md
View File

@ -11,9 +11,7 @@ Since I wanted to get this done sooner rather than later, instead of waiting for
Creating a zpool on the drive itself is pretty easy. I plugged it into a computer with ZFS tools installed and ran this:
```
sudo zpool create -o ashift=13 -o autoexpand=on -o autotrim=on -O canmount=off -O mountpoint=none -O compression=on -O checksum=sha256 -O xattr=sa -O acltype=posix -O atime=off -O relatime=on coldstorage /dev/sdb
```
sudo zpool create -o ashift=13 -o autoexpand=on -o autotrim=on -O canmount=off -O mountpoint=none -O compression=on -O checksum=sha256 -O xattr=sa -O acltype=posix -O atime=off -O relatime=on coldstorage /dev/sdb
This command complained about the extant exFAT the drive came with; rerunning with `-f` wiped it clean.
@ -21,15 +19,11 @@ This command complained about the extant exFAT the drive came with; rerunning wi
`man zfs-send` seems to prefer sending snapshots, which makes sense: you don't have to think about sending updates if changes are happening during the send. Let's check what snapshots we have:
```
zfs list -t snapshot
```
zfs list -t snapshot
The last snapshot was taken 2023-01-09. Better make a new one.
```
zfs snapshot -r pool@2023-08-30
```
zfs snapshot -r pool@2023-08-30
`-r` makes the snapshot recursive, so all the datasets within `pool` are also snapshotted.
@ -39,22 +33,16 @@ We're going to pipe the data over SSH, which means we need the user account to h
On the sending side, I had to give myself these:
```
zfs allow -u tvb send,snapshot,hold pool
```
zfs allow -u tvb send,snapshot,hold pool
On the receiving side:
```
zfs allow -u tvb compression,mountpoint,create,mount,receive,sharenfs,userprop,atime,recordsize coldstorage
```
zfs allow -u tvb compression,mountpoint,create,mount,receive,sharenfs,userprop,atime,recordsize coldstorage
There might have been more; basically any property set on the pool or datasets needs to be allowed on the receiving side, since those properties are being created or modified on the destination ZFS.
Now we can send the data:
```
ssh nas.lan zfs send -R pool@2023-08-30 | pv | zfs recv -s coldstorage/pool
```
ssh nas.lan zfs send -R pool@2023-08-30 | pv | zfs recv -s coldstorage/pool
And that's all it takes. I am not a ZFS expert by any means, but on the whole the experience here was pretty painless. I spent a lot of time reading the man pages, which did a good job explaining what I needed to know.
And that's all it takes. I am not a ZFS expert by any means, but on the whole the experience here was pretty painless. I spent a lot of time reading the man pages, which did a good job explaining what I needed to know.