Re: [Nbd] input/output error
- To: "nbd-general@lists.sourceforge.net" <nbd-general@lists.sourceforge.net>
- Subject: Re: [Nbd] input/output error
- From: Raphael Bauduin <rblists@...17...>
- Date: Wed, 2 Oct 2013 16:03:30 +0200
- Message-id: <CAONrwUFyLjrCGdQGk32zL+UF8vNktdt5UXJEukJVzedB9J46mg@...18...>
- In-reply-to: <CAONrwUFLuPE-YfHkje8dLH9k4RTYTtAz=DFu1q00ROkaykM_fQ@...18...>
- References: <CAONrwUFLuPE-YfHkje8dLH9k4RTYTtAz=DFu1q00ROkaykM_fQ@...18...>
I managed to reproduce it and get some more info. I wonder if the problem comes from the snapshot feature of qemu-nbd and will search further in that direction. Here is some more info
in cas it might be useful
When the problem occurs (the rsync cannot sync some file), here the error found in dmesg, and that for each file inaccessible:
[10281712.036554] block nbd0: Other side returned error (30)
[10281712.036626] end_request: I/O error, dev nbd0, sector 2048
[10281712.036672] Buffer I/O error on device nbd0p1, logical block 0
[10281712.045150] lost page write due to I/O error on nbd0p1
[10281712.045202] EXT4-fs error (device nbd0p1): ext4_lookup:1050: inode #265035: comm rsync: deleted inode referenced: 261670
[10281712.067196] EXT4-fs (nbd0p1): previous I/O error to superblock detected
Seems the inode had been deleted from the snapshot connected in read only mode!
Unmounting and remounting the nbd device gives a problem:
[10282154.368609] EXT4-fs (nbd0p1): INFO: recovery required on readonly filesystem
[10282154.368615] EXT4-fs (nbd0p1): write access unavailable, cannot proceed
This leads me to think that the problem is not with nbd, but with the snapshot taking feature of qemu-nbd. Correct me if I'm wrong! ;-)
Raph
Reply to: