I did an install FreeBSD 10 from stick image using the ZFS on root option to 2 ssd drives which went smoothly. After reading more will add a third ssd.
Having a little trouble comprehending what I am looking at, my last system was release 6.
If I try to see whether trim is active through say, tunefs or other tools, I can't seem to identify what the drives actually are.
this also means I cannot figure out how to mount these drives from a livecd boot to say perform recovery etc as I can't identify them properly.
gives me a lot of interesting info, as does
but, I am at a loss how to use this information to either find the state of trim or to mount the drives when booting from alternate (livecd) boot for future maintenance.
I thought to go back to adding the ZFS to a single drive booted system, but I like the idea of fully mirrored, and and hoping that release 10 has gotten past many of the issues I have been reading about. A lot of the documentation has not seemed to have caught up, so it's hard to tell.
Any pointers greatly appreciated!
OK! - Half my question I found an answer to:
Checking trim ZFS found in post -
FreeBSD 10 Trim for ZFS
Postby meteor8488 » 08 Feb 2014, 18:04
this gets the trim answer.
Still stuck on how to grasp the mount in this system or from a LiveCD boot......
Having a little trouble comprehending what I am looking at, my last system was release 6.
If I try to see whether trim is active through say, tunefs or other tools, I can't seem to identify what the drives actually are.
this also means I cannot figure out how to mount these drives from a livecd boot to say perform recovery etc as I can't identify them properly.
Code:
# mount
zroot/ROOT/default on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
zroot/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
zroot/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)
zroot/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls)
zroot/usr/src on /usr/src (zfs, local, noatime, noexec, nosuid, nfsv4acls)
zroot/var on /var (zfs, local, noatime, nfsv4acls)
zroot/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nfsv4acls)
zroot/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls)
zroot/var/mail on /var/mail (zfs, local, nfsv4acls)
zroot/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
Code:
# zfs mount
zroot/ROOT/default /
zroot/tmp /tmp
zroot/usr/home /usr/home
zroot/usr/ports /usr/ports
zroot/usr/src /usr/src
zroot/var /var
zroot/var/crash /var/crash
zroot/var/log /var/log
zroot/var/mail /var/mail
zroot/var/tmp /var/tmp
Code:
# zpool get all
Code:
# egrep 'ada[1-9]' /var/run/dmesg.boot
ada0 at ahcich2 bus 0 scbus0 target 0 lun 0
ada0: <Samsung SSD 840 EVO 120GB EXT0BB6Q> ATA-9 SATA 3.x device
ada0: Serial Number S1D5NSAF371827E
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 512bytes)
ada0: Command Queueing enabled
ada0: 114473MB (234441648 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
ada1 at ahcich4 bus 0 scbus1 target 0 lun 0
ada1: <Samsung SSD 840 EVO 120GB EXT0BB6Q> ATA-9 SATA 3.x device
ada1: Serial Number S1D5NSAF371702X
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 512bytes)
ada1: Command Queueing enabled
ada1: 114473MB (234441648 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad6
but, I am at a loss how to use this information to either find the state of trim or to mount the drives when booting from alternate (livecd) boot for future maintenance.
I thought to go back to adding the ZFS to a single drive booted system, but I like the idea of fully mirrored, and and hoping that release 10 has gotten past many of the issues I have been reading about. A lot of the documentation has not seemed to have caught up, so it's hard to tell.
Any pointers greatly appreciated!
OK! - Half my question I found an answer to:
Checking trim ZFS found in post -
FreeBSD 10 Trim for ZFS
Postby meteor8488 » 08 Feb 2014, 18:04
Code:
# sysctl vfs.zfs.trim
# sysctl -d kstat.zfs.misc.zio_trim
# sysctl -a |grep _trim
Still stuck on how to grasp the mount in this system or from a LiveCD boot......