Arch Linux

mabra

Member

From: Brühl

Registered: 2015-10-05

Posts: 22

ARCH/ZFS on boot: Some errors to evaluate

Hello !

I probably going from Debian to Arch - will see, and so, have a first
Arch setup as a VM and ZFS is on boot.

Everythings works as expected, but there are two messages, which
gives me questions:

In the boot process at the console and the bootlog, I see:
>systemd: starting import zfs pools by device scanning
>zpool: no pools available to import
>systemd: started import zfs pool by device scanning
>systemd: starting mount of zfs filesystems

Is this for pools, which may have been added AFTER install ?
I could insert new disk after setup, which are from another machine
and contains a pool - I could image, that the scan above is for
this reason, but dont exactly now.
As said, the pool is there, status ok and filesystems usable -
except to the following.

But there might be a problem with attributing the pool. What
I see later in the log, does not look pretty:
>systemd: starting volatile filesystems and directories
>systemd-tempfiles: cannot set fileattribute for '/var/log/journal',
    value=0x00800000, mask=0x00800000, operation not supported

The perms on var as follows:
drwxr-xr-x  root  root  var

The properties of ZFS, which may have effect here:
syspool xattr=on
syspool aclinherit=restricted
syspool xattr=on
syspool acltype=off

I have not set these properties at install time. I changed these
properties for the pool and rebootet, but the problem remains.

I have /root and /home as zfs-filesystems, but no extra filesystem
for /var - so, according to arch's zfs wiki, I should not worry.

What probably belongs to the shown errors is, that there are apps,
like the snmpd, which appear as follwoing in journal logs:

systemd[1]: Starting Simple Network Management Protocol (SNMP) Daemon...
systemd[1]: snmpd.service: PID file /run/snmpd.pid not readable (yet?) after start: No such file or directory
systemd[1]: Started Simple Network Management Protocol (SNMP) Daemon.

The process runs and it's pid file contains the right pid.

I installed from archiso [227], have kernel 4.2.5-1.

Help/explanation would really be great !

Thanks anyway,

Manfred

loqs

Member

Registered: 2014-03-06

Posts: 18,311

Re: ARCH/ZFS on boot: Some errors to evaluate

systemd: starting volatile filesystems and directories
systemd-tempfiles: cannot set fileattribute for '/var/log/journal',
	value=0x00800000, mask=0x00800000, operation not supported

That is caused by /usr/lib/tmpfiles.d/journal-nocow.conf as stated zfs does not support setting nocow like that.
From the tmpfiles.d man page

If the administrator wants to disable a configuration file supplied by
       the vendor, the recommended way is to place a symlink to /dev/null in
       /etc/tmpfiles.d/ bearing the same filename.

Edit:

In the boot process at the console and the bootlog, I see:
>systemd: starting import zfs pools by device scanning
>zpool: no pools available to import
>systemd: started import zfs pool by device scanning
>systemd: starting mount of zfs filesystems

Is this for pools, which may have been added AFTER install ?
I could insert new disk after setup, which are from another machine
and contains a pool - I could image, that the scan above is for
this reason, but dont exactly now.
As said, the pool is there, status ok and filesystems usable -
except to the following.

This thread might explain it
https://bbs.archlinux.org/viewtopic.php … 3#p1520833

Last edited by loqs (2015-11-17 23:53:08)

mabra

Member

From: Brühl

Registered: 2015-10-05

Posts: 22

Re: ARCH/ZFS on boot: Some errors to evaluate

Hello !

Thanks for your reply - I am aware of this, but would like to have better info.

As like in the mentioned threads was shown, it is a problem with the attributes.
I have verified, the the problem occured, applying: >chattr +C /var/log
I tried this into an empty directory and it was working, once ! I could not
repeat it and the attribute was not to see - so, probably not really set.
But I could not do it a second time. Then I created a new zfs filesystem
and was able to reproduce it - once, again, without beeing able the see
the attribute.
Additionally, there was a loud debate in 2010 about the aclmode property
of ZFS. I tried to set it to 'passthrough', but got: 'invalid property', even
though, it is in the documentation ....
Anyway, used the given "patch" and the errors disappear. "C+" should
only effect performance.

Thanks for your help.

Best regards,

Manfred