-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] mfsbdev and map + unmap + map on /dev/ndb0 = input/output error #551
Comments
asyslinux
changed the title
[BUG] mfsdbev and map + unmap + map on /dev/ndb0 = input/output error
[BUG] mfsbdev and map + unmap + map on /dev/ndb0 = input/output error
Sep 17, 2023
Thank you for the report. We've found the issue and we will post a fix soon! |
acid-maker
added a commit
that referenced
this issue
Oct 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you read through available documentation, open Github issues and Github Q&A Discussions?
Yes
System information
Debian 11.7 (amd64) + Proxmox 7.4 / MooseFS Pro 3.0.117
root@srv:~# uname -a
Linux srv 5.15.116-1-pve #1 SMP PVE 5.15.116-1 (2023-08-29T13:46Z) x86_64 GNU/Linux
Hardware / network configuration, and underlying filesystems on master, chunkservers, and clients.
Underlying fs: ext4
2 x master server
2 x chunkservers
2 x clients
How much data is tracked by moosefs master (order of magnitude)?
Empty, new MooseFS.
Describe the problem you observed.
I try to use mfsbdev for virtual machine images. But before i start use this for vm, i have a problem:
When i start mfsbdev and 1. map file 2. unmap file 3. map file again , then ndb device is not working properly anymore.
If i stop and start mfsbdev, map is start normally and working ok. But if i have several vm`s, then i can not stop mfsbdev service in production ready system, because i need to stop all virtual machines, in this case.
VM is stopped (vm is not important now).
map + unmap + map uses only /dev/nbd0
Additional settings:
Can you reproduce it? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Yes:
Also strange size of partition = 238.4G in 32GB disk
/dev/mfs/vm-wire-lv1 * 2048 62498815 62496768 238.4G 83 Linux
After map + unmap + map and get input/output error, then if try to repeat additional unmap + map, then working ok, without restart mfsbdev service.
And if try to repeat one more unmap + map, then get again input/output error.
I mean:
map = ok
map + unmap + map = input/output error
map + unmap + map + unmap + map = ok
map + unmap + map + unmap + map + unmap + map = input/output error
map + unmap + map + unmap + map + unmap + map + unmap + map = ok
Additionally:
Also i try to use -i for ignore locking, but this is not working too. I have an idea - map single image on 2 different servers with -i key for ready hot standby scenario for vm`s, but if i stop vm on 1-st server and unmap file of vm on 1-st server, then on 2-nd server i also see input/output error when i try to use fdisk/cfdisk.
I have two servers in MooseFS Pro cluster with mfsbdev and want to have hot standby scenario for virtual machines with -i key (ideal solution with pre-mapped image files on 2-nd server) or without -i key, if this is impossible to have more than 1 ndb mapped devices with single image on 2 different servers in cluster - in this case i can manually map ndb devices before start vm`s on 2-nd server if 1-st server is going down.
But now, simple map + unmap + map = broken ndb device on single server too.
After stopping mfsbdev and removing nbd module from kernel, i also see stuck connections:
The text was updated successfully, but these errors were encountered: