Skip to content
This repository has been archived by the owner on Jan 2, 2025. It is now read-only.

Mount of a snapshot device with XFS is failing time to time on Debian 8 #139

Closed
e-kov opened this issue Jun 14, 2022 · 0 comments · Fixed by #158
Closed

Mount of a snapshot device with XFS is failing time to time on Debian 8 #139

e-kov opened this issue Jun 14, 2022 · 0 comments · Fixed by #158
Assignees
Labels
bug Something isn't working project/data-plane xfs

Comments

@e-kov
Copy link
Collaborator

e-kov commented Jun 14, 2022

Mount of a snapshot device with XFS is failing time to time on Debian 8, kernel 3.16.0-11-amd64

mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or helper program, or other error

dmesg:

[  115.291938] elastio-snap: module init
[  115.291942] elastio-snap: get major number
[  115.291944] elastio-snap: allocate global device array
[  115.291945] elastio-snap: registering proc file
[  115.291951] elastio-snap: registering control device
[  115.292118] elastio-snap: locating system call table
[  115.292122] elastio-snap: system call table located at 0xffffffff81601680
[  115.736871] elastio-snap: detected block device mount: /dev/loop0 -> /tmp/elastio-snap_172 : 0xc0ed0000
[  115.753289] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[  115.754835] XFS (loop0): Superblock has unknown read-only compatible features (0x4) enabled.
[  115.755626] XFS (loop0): Attempted to mount read-only compatible filesystem read-write.
Filesystem can only be safely mounted read only.
[  115.755636] XFS (loop0): SB validate failed with error 22.
[  115.757261] elastio-snap: mount returned: -22

Probably better to tackle with this issue after #63

@e-kov e-kov added bug Something isn't working project/data-plane labels Jun 14, 2022
e-kov pushed a commit that referenced this issue Jun 15, 2022
This modification for the tests was done long time ago in scope of draft for #63
It allows to run `tests/elio-test.sh` with the file system specified as an argument.
Now tests can be executed like this
```bash
# Run tests, as usually, on the loop device and ext4 filesystem
sudo ./elio-test.sh

# Run tests on the loop device and ext3 filesystem
sudo ./elio-test.sh -f ext3

# Run tests on the /dev/vdb1 device and XFS filesystem
sudo ./elio-test.sh -d /dev/vdb1 -f xfs
```

The test `test_track_writes` is disabled for XFS due to #63.
And all the tests for XFS were disabled on Debian 8 due to the mount issue
(created new bug #139) and on Ubuntu 22.04 due to the issue with destroy
of unverified snapshot and incremental (see new bug #138).
@e-kov e-kov self-assigned this Aug 8, 2022
@e-kov e-kov added the xfs label Aug 8, 2022
e-kov pushed a commit that referenced this issue Aug 12, 2022
Fore some reason (probably for viy) we have to new manually installed
xfsprogs on the Debian 8 boxes. Fixed it by xfsprogs and libs
re-install.

And udjusted work with `mdadm` utility in tests to work on old ( < 3.5)
Python.

Resolves #139
e-kov pushed a commit that referenced this issue Aug 15, 2022
Fore some reason (probably for viy) we have to new manually installed
xfsprogs on the Debian 8 boxes. Fixed it by xfsprogs and libs
re-installation.

And adjusted work with `mdadm` utility in tests to work on old ( < 3.5)
Python.

No changes in the driver.

Resolves #139
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working project/data-plane xfs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant