The "sys_path_to_bdev() failed for path [.]!" error has already been
posted upstream 5 years ago
(https://bugzilla.samba.org/show_bug.cgi?id=10541), yet this error still
shows up. It doesn't do harm in my setup, but it's annoying and clutters
the logs. I've done some Google-Fu on this matter and I
There's a hacky workaround to disable quotas that makes the error vanish
from the logs. Not sure of sideeffects.
Put a line like this into your smb.conf [global] to point it to the attached
script
get quota command = /opt/bin/samba-btrfs-quota.sh
The script will then tell samba on each
Same bug on 18.04 samba + btrfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage notifications about this bug go to:
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage notifications about this
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage notifications about this bug go to:
When you use the uid/gid options, do all files in the share get owned by
that uid/gid?
Can you check the output of the mount command after mounting the share,
with and without uid/gid, and see which options ended up being used?
That output will include defaults that you did not specify.
For
Oh, and I meant to add that this NAS is using btrfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage notifications about this bug go to:
When you use the uid/gid options, do all files in the share get owned by
that uid/gid?
Can you check the output of the mount command after mounting the share,
with and without uid/gid, and see which options ended up being used?
That output will include defaults that you did not specify.
For
Oh, and I meant to add that this NAS is using btrfs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage notifications about this bug
I was mistaken about the cause of this bug. It appears that some default
setting has changed, and cifs mounts need uid and gid options passed
explicitly. In previous Ubuntu versions, I could mount cifs with just
credentials provided I set the owners of the mount point and remote
files correctly, a
Yes, it's on a btrfs partition in line with the samba bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage notifications about this bug go to:
Are you using btrfs, zfs and/or xfs on the server where the exported
share is?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage
Are you using btrfs, zfs and/or xfs on the server where the exported
share is?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage notifications about
** Package changed: ubuntu => samba (Ubuntu)
** Bug watch added: Samba Bugzilla #10541
https://bugzilla.samba.org/show_bug.cgi?id=10541
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=10541
Importance: Unknown
Status: Unknown
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
15 matches
Mail list logo
