I've experimented with this on eoan and focal (ZFS 0.8.1 and ZFS 0.8.3)
on a 4GB VM image. I set the /etc/modprobe.d/zfs.conf as follows:
options zfs zfs_arc_max=134217728
# 128 MB
And rebooted. I then exercised the zfs with various greps and git logs
on the linux git repository while running:
I moved to Ubuntu 20.04 and I do not have that problem anymore.
I stopped with writing directly after the login the value to the file
/sys/module/zfs/parameters/zfs_arc_max.
I now only rely on "options zfs zfs_arc_max=3221225472" in
/etc/modprobe.d/zfs.conf.
Problem solved in 20.04 and I tried i
I'll close this bug report if that's OK.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854480
Title:
zfs_arc_max not working anymore in zfs 0.8.1
Status in zfs-linux package in Ub
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854480
Title:
zfs_arc_max not working anymore in zfs 0.8.1
** Description changed:
In the past I could limit the size of L1ARC by specifying "options zfs
zfs_arc_max=3221225472" in /etc/modprobe.d/zfs.conf. I tried even to
- fill /sys/module/zfs/parameters/zfs_arc_max directly after login, but
- none of those methods limits the size of L1ARC. It worke
I would like to reopen this issue. I installed Ubuntu 20.04.1 LTS Server
(no zfs root, 16GB RAM) and added zfs volumes. I tried to limit the arc
with
`options zfs zfs_arc_max=134217728` in `/etc/modprobe.d/zfs.conf` to
128MiB (just to try)
I updated the initial ramdisk with `update-initramfs -u`
The `zfs_arc_max` setting *is* respected when I set it to a value of
`1073741824` = 1GiB
```
cat /etc/modprobe.d/zfs.conf; cat /sys/module/zfs/parameters/zfs_arc_max; cat
/proc/spl/kstat/zfs/arcstats |grep ^size -B3
options zfs zfs_arc_max=1073741824
1073741824
c 4
The limit in the code does seem to be 64 MiB. I'm not sure why this
isn't working. I am not even close to an expert on this part of OpenZFS,
so all I can suggest is to file a bug report upstream:
https://github.com/openzfs/zfs/issues/new
--
You received this bug notification because you are a mem
Maybe I'm missing something here. I tested this out on an Eoan server:
$ dmesg | grep ZFS
[ 10.821332] ZFS: Loaded module v0.8.1-1ubuntu14.3, ZFS pool version 5000,
ZFS filesystem version 5
$ uname -a
Linux eaon-amd64 5.3.0-42-generic #34-Ubuntu SMP Fri Feb 28 05:49:40 UTC 2020
x86_64 x86_64
Yes you did miss something. Of course the value is changed in
/etc/modprobe.d/zfs.conf. I changed it myself! However zfs is ignoring
that value and is using considerably more memory for L1ARC.
If I wanted to limit the size of L1ARC, I had to change the value in
/sys/module/zfs/parameters/zfs_arc_m
Just for clarification, how are you determining that zfs is using more
memory for the L1ARC?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854480
Title:
zfs_arc_max not working any
I display it constantly using conky (see attachment) and conky is using
${color}L1ARC / ${color0}Hits%: ${color}${alignr}(${exec cat
/proc/spl/kstat/zfs/arcstats | grep -m 1 uncompressed_size | awk
'{printf "%4.2f",$3/1073741824}'}) ${exec cat
/proc/spl/kstat/zfs/arcstats | grep -m 1 size | awk '{
OK, close the bug-report.
On Thu, 2020-03-26 at 22:47 +, Colin Ian King wrote:
> I'll close this bug report if that's OK.
>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854480
13 matches
Mail list logo
