rambo Eero af Heurlin
Jaikus from rambo
Sunday, 1 February 2009
-
True, indeed first-class. Can't wait for the rest of the episodes.
Saturday, 31 January 2009
Wednesday, 28 January 2009
-
I guess using the wrong error code is on par with the general clue level of 'multifail'. "It works on multiple levels", or in this case fails.
-
I still wonder why it wasn't 500 multifail ?
Tuesday, 27 January 2009
-
The point being that I'm finally going to repair my RC heli.
Friday, 23 January 2009
-
and that would be "as storage server" not "ad storage server"
-
And for future reference the error when trying to set bootfs on raidz (prior to this I had created the pool and copied with
zfs send -Rfull history of syspool/rootfs-nmu-000 to rootpool/rootfs-nmu-000):zfs set bootfs=rootpool/rootfs-nmu-000 rootpoolgives error "No such pool or dataset" even though both the pool and dataset both obviously exist, in fact changing the filesystem name to -001 for example gives a different error (invalid name AFAIRecall). -
Since the only "real" SSDs verkkokauppa had in stock were 1. too large in capasity 2. hence too expensive. So I got a 4GB high-speed microSDHC card which came with very compact USB card reader.
Handily the SuperMicro motherboard also has one standard USB port (in addition to many pin headers as is usual) directly on the inside of the case. So in goes the reader, adjust boot order and install Nexenta on the card. Then
zfs set atime=off syspool/rootfs-nmu-000and create new swap "partition" on the raidz pool and switch to use that for swap (not that I expect much swapping, the system has 8G RAM which will be mainly used for disk cache [intended ad storage server]).Installing on the "usb disk" the sd card and reader represent was not completely without hitches, it seems the installer creates a zfs pool 'tmp' which it destroys, but in this case it was not properly destroyed and in stead was missing vdevs causing dire warnings from the kernel.
zpool destroy tmpgot rid of those for good. Wednesday, 21 January 2009
-
found the reason: booting from raidz pools is not possible. but the error message was really useless. next up: decide which approach is best for making minimal boot fs while placing everything else on the raidz pool.
-
So I added another disk and installer Nexenta on that, and created a raidz2 pool on the 8 disks I was planning to use. But couldn't yet figure out how to make the new pool bootable (zpool refuses to set the bootfs parameter for some weird reason).
Tuesday, 20 January 2009
Monday, 19 January 2009
Friday, 16 January 2009
-
taxi home - ~25Eur panadol- "free" water (~1l) - "free" normipäivä beginning with a meeting - priceless
Wednesday, 14 January 2009
Saturday, 10 January 2009
Wednesday, 7 January 2009
Jaikus from rambo