NetBSD-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Zfs on NetBSD
Because I don't like loose ends, I thought I would follow-up (update) the zfs issue.
I did make my system 8.99.51, user land included. Zfs worked as expected
I did a fresh (new) install of 9BETA and zfs works as expected, no errors.
Just wanted to thank everyone for their help and input.
$ sudo zpool create -f monastery mirror /dev/wd1d /dev/wd2d
$ sudo zpool status
pool: monastery
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
monastery ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
wd1d ONLINE 0 0 0
wd2d ONLINE 0 0 0
errors: No known data errors
$ mount
/dev/dk2 on / type ffs (local)
kernfs on /kern type kernfs (local)
ptyfs on /dev/pts type ptyfs (local)
procfs on /proc type procfs (local)
tmpfs on /var/shm type tmpfs (local)
monastery on /monastery type zfs (local)
$ df -h
Filesystem Size Used Avail %Cap Mounted on
/dev/dk2 1.7T 86G 1.6T 5% /
kernfs 1.0K 1.0K 0B 100% /kern
ptyfs 1.0K 1.0K 0B 100% /dev/pts
procfs 4.0K 4.0K 0B 100% /proc
tmpfs 8.0G 4.0K 8.0G 0% /var/shm
monastery 1.8T 23K 1.8T 0% /monastery
$ sudo zfs list
NAME USED AVAIL REFER MOUNTPOINT
monastery 72.5K 1.76T 23K /monastery
$ sudo zfs create monastery/data
$ sudo zfs create monastery/vimages
$ sudo zfs list
NAME USED AVAIL REFER MOUNTPOINT
monastery 126K 1.76T 23K /monastery
monastery/data 23K 1.76T 23K /monastery/data
monastery/vimages 23K 1.76T 23K /monastery/vimages
$ mount
/dev/dk2 on / type ffs (local)
kernfs on /kern type kernfs (local)
ptyfs on /dev/pts type ptyfs (local)
procfs on /proc type procfs (local)
tmpfs on /var/shm type tmpfs (local)
monastery on /monastery type zfs (local)
monastery/data on /monastery/data type zfs (local)
monastery/vimages on /monastery/vimages type zfs (local)
On 7/28/19, 9:11 AM, "Chavdar Ivanov" <ci4ic4%gmail.com@localhost> wrote:
On second thought, ' zpool scrub' worked as expected; the amount
initially copied was not enough to notice it.
It does tak a lot of memory, though - as expected, during the tar copy:
...
Memory: 8387M Act, 4101M Inact, 40K Wired, 38M Exec, 12G File, 31M Free
... (on a 20GB laptop).
On Sun, 28 Jul 2019 at 12:35, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>
> For quite a while I hadn't tried ZFS under NetBSD; it used to crash
> for me years ago under load and didn't seem much in the focus of the
> development, I think it is fair to say. Following this thread, I
> decided to give it a go. There was presently unused 32GB mSATA card in
> one of my laptops, which I unmounted; there was no need to clean the
> labels at all.
> On -current 8.99.51 from a few days ago everything seem to be working
> fine for me:
> ...
> modload zfs
> modstat zfs
> zpool create tank /dev/wd2d
> zpool status
> df -k
> ls -la /tank
> zfs create tank/t1
> zfs create tank/t2
> zfs create tank/t3
> df -k
> zpool status
> zpool scrub tank
> zpool status
> .....
> Some 13GB worth of packages were also tarred over with reasonable speed.
>
> I am not sure if 'zpool scrub' actually does something, though - even
> when there is some data on the disk, the subsequent 'zpool status'
> claims the scrub has finished straight away:
> ...
> # zpool status tank
> pool: tank
> state: ONLINE
> scan: scrub repaired 0 in 0h0m with 0 errors on Sun Jul 28 13:23:47 2019
> config:
>
> NAME STATE READ WRITE CKSUM
> tank ONLINE 0 0 0
> wd2d ONLINE 0 0 0
>
> errors: No known data errors
> # zpool scrub tank
> # zpool status tank
> pool: tank
> state: ONLINE
> scan: scrub repaired 0 in 0h0m with 0 errors on Sun Jul 28 13:32:08 2019
> config:
>
> NAME STATE READ WRITE CKSUM
> tank ONLINE 0 0 0
> wd2d ONLINE 0 0 0
>
> errors: No known data errors
> ......
>
> Chavdar
>
> On Sun, 28 Jul 2019 at 07:54, Greg Troxel <gdt%s1.lexort.com@localhost> wrote:
> >
> > Ron Georgia <netverbs%gmail.com@localhost> writes:
> >
> > > Yes, I do have /dev/zfs.
> > > $ ll /dev/zfs
> > > crw------- 1 root wheel 190, 0 Jul 21 15:23 /dev/zfs
> > >
> > > I did find the zfs.mod, but get this error when trying to load it.
> > > $ sudo modload /stand/amd64/8.1/modules/zfs/zfs.kmod
> > > modload: /stand/amd64/8.1/modules/zfs/zfs.kmod: Program version wrong
> > >
> > > Which makes sense since I am booting kernel 8.99.51 NetBSD 8.99.51 (GENERIC)
> > > I did pull down the sets for NetBSD 8.99.51 (GENERIC) and unpacked base.tar.xz and modules.tar.xz. Then I copied the contents of stand to /stand/amd64/8.99.51. (Should I remove /stand/amd64/8.1?)
> >
> > Basically, you need consistent kernel and modules. So if you have moved
> > to current permanently, yes, delete the 8.1 modules.
> >
> > Also, to run current zfs, it seems overwhelmingly likely that you want
> > to run the zfs userland binaries from current, not from 8.1.
> >
> > You may want to look at the various schemes for in-place updating, such
> > as INSTALL-NetBSD from pkgsrc/sysutils/etcmanage (my take on how to do
> > it), and sysupgrade (somebody else's take).
> >
> > I unpack all the sets except etc/xetc, unpack etc/xetc into
> > /usr/netbsd-etc, and then merge the etc changes.
> >
> > > [ 11951.1654531] WARNING: module error: module `zfs' built for `801000000', system `899005100'
> > > [ 12310.9533135] WARNING: module error: module `zfs' built for `801000000', system `899005100'
> > > [ 12509.3029082] WARNING: module error: recursive load failed for `zfs' (`solaris' required), error 2
> > > [ 30.9168505] WARNING: module error: incompatible module class for `zfs' (3 != 2)
> > > [ 30.9769426] WARNING: module error: incompatible module class for `zfs' (3 != 2)
> >
> > That really looks like you are loading 8.1 modules. rm them, and maybe
> > you will get a different error.
> >
>
>
> --
> ----
--
----
Home |
Main Index |
Thread Index |
Old Index