schnapps issueshttps://gitlab.nic.cz/turris/schnapps/-/issues2021-10-20T09:34:16+02:00https://gitlab.nic.cz/turris/schnapps/-/issues/46using other root option throws ntfs errors2021-10-20T09:34:16+02:00th1j5using other root option throws ntfs errorsI tried to use schnapps instead of the lower-level btrfs tools to snapshot my (RAID) btrfs filesystem, by using the `-d root` option.
Then I get weird ntfs-3g errors...
```sh
root@turris:/mnt# btrfs sub list /mnt/DATA_NAS/
ID 256 gen 15...I tried to use schnapps instead of the lower-level btrfs tools to snapshot my (RAID) btrfs filesystem, by using the `-d root` option.
Then I get weird ntfs-3g errors...
```sh
root@turris:/mnt# btrfs sub list /mnt/DATA_NAS/
ID 256 gen 1570 top level 5 path @
ID 260 gen 29 top level 5 path @DATA_other
ID 261 gen 1572 top level 5 path @DATA_NAS
```
```
root@turris:/mnt# schnapps -d "/mnt/DATA_NAS" list
ERROR: unable to access /dev/sdb
/dev/sda: No such file or directory
ntfs-3g: Failed to access volume '/dev/sdb
/dev/sda': No such file or directory
ntfs-3g 2017.3.23 integrated FUSE 27 - Third Generation NTFS Driver
Configuration type 1, XATTRS are on, POSIX ACLS are off
Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2017 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson
Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
Options: ro (read-only mount), windows_names, uid=, gid=,
umask=, fmask=, dmask=, streams_interface=.
Please see the details in the manual (type: man ntfs-3g).
Example: ntfs-3g /dev/sda1 /mnt/windows
News, support and information: http://tuxera.com
Can't mount root partition
```
It would be nice to use schnapps as a high-level tool, so if I can provide any other information, let me know.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/schnapps/-/issues/44SMB1 mounts are not supported2021-10-20T09:34:48+02:00Michal VasilekSMB1 mounts are not supportedTrying to mount a Synology NAS, I get this error:
```
mount error(95): Not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Can't access remote filesystem
root@omnia:~# dmesg
...
[ 56...Trying to mount a Synology NAS, I get this error:
```
mount error(95): Not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Can't access remote filesystem
root@omnia:~# dmesg
...
[ 5686.349245] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
```
Adding `-o vers=1.0` to the mount.cifs command fixes this issue for me. I think the defaults are correct now, maybe adding an option (with a warning) to use the 1.0 version or documenting this would make life easier for some people. If this is the default behavior of some (?) older (?) Synology NASes, this issue would be common.
Either way, I think this message in dmesg is logged even when the server supports SMB3, so it should probably be silenced with `-o vers=default`.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/schnapps/-/issues/41Lock file is left in /tmp in rescue SSH shell2021-08-13T09:34:29+02:00petrcechLock file is left in /tmp in rescue SSH shellSchnapps do not remove LOCK directory in `/tmp` when started in rescue mode 5.
The reason is missing `rmdir` command in busybox.
----------------------------------------------------
Zdravím,
při startu MOXe a režimu 5 - ssh na 192.168...Schnapps do not remove LOCK directory in `/tmp` when started in rescue mode 5.
The reason is missing `rmdir` command in busybox.
----------------------------------------------------
Zdravím,
při startu MOXe a režimu 5 - ssh na 192.168.1.1 nemaže schnapps LOCK-adresář v /tmp.
Příčinou je chybějící rmdir příkaz v busyboxu. "Testováno" po pokusu aktualizovat pár balíčku v Turris 6.0 a následném zamrznutí.
rm -rf je podporováno
PetrMichal HruseckyMichal Hrusecky