although I'm not using XPEnology but rather a stock DS218 with DSM 7.1, I'm asking this question here because a vaguely similar question has been asked and answered really competently here before.
The situation with me is different in the sense that the cause of the error can be traced back to the creation of a snapshot for a specific shared folder (/volume1/homes). This snapshot has been created for years every hour, but a few days ago the creation resulted in this problem (no reboot or any other noticeable problem occurred during the hour between the last working snapshot and the one that triggered the problem):
The rest of the system is running perfectly fine, so once I disable the snapshot for this specific folder, no error messages occur and a 19 hour extended S.M.A.R.T. test returns no failures on both disks. I haven't done data scrubbing ever so far, but have done it now which also completes without any warnings. But as soon as I execute either a planned or manual snapshot of /volume/homes, the system immediately goes into write-protected mode and system status turns to critical. I can then reboot, set the system to read-write again, reboot again and everything is fine again with no errors for days.
I have also written a tar file of /volume/homes on the same disc in order to have another backup and then moved it to external storage. No error occurred during the creation of this archive.
This is the output of /var/log/messages once the error occurs:
I assume that there is some btrfs transaction that gets triggered or replayed once the folder is accessed, but I don't understand why this did not get triggered when I created the tar file from the same folder.
I guess that there is some kind of btrfs command that would deal with this, but I don't want to just use any of the commands mentioned in the post above without knowing if it is applicable in my situation. Most importantly, I would like to know if it's possible to find out which file caused this problem and/or which files have actually been affected by this problem so I can get them back from backup.
Question
freetz
Hi everyone,
although I'm not using XPEnology but rather a stock DS218 with DSM 7.1, I'm asking this question here because a vaguely similar question has been asked and answered really competently here before.
The situation with me is different in the sense that the cause of the error can be traced back to the creation of a snapshot for a specific shared folder (/volume1/homes). This snapshot has been created for years every hour, but a few days ago the creation resulted in this problem (no reboot or any other noticeable problem occurred during the hour between the last working snapshot and the one that triggered the problem):
The rest of the system is running perfectly fine, so once I disable the snapshot for this specific folder, no error messages occur and a 19 hour extended S.M.A.R.T. test returns no failures on both disks. I haven't done data scrubbing ever so far, but have done it now which also completes without any warnings. But as soon as I execute either a planned or manual snapshot of /volume/homes, the system immediately goes into write-protected mode and system status turns to critical. I can then reboot, set the system to read-write again, reboot again and everything is fine again with no errors for days.
I have also written a tar file of /volume/homes on the same disc in order to have another backup and then moved it to external storage. No error occurred during the creation of this archive.
This is the output of /var/log/messages once the error occurs:
and this is the output of dmesg at that time:
I assume that there is some btrfs transaction that gets triggered or replayed once the folder is accessed, but I don't understand why this did not get triggered when I created the tar file from the same folder.
I guess that there is some kind of btrfs command that would deal with this, but I don't want to just use any of the commands mentioned in the post above without knowing if it is applicable in my situation. Most importantly, I would like to know if it's possible to find out which file caused this problem and/or which files have actually been affected by this problem so I can get them back from backup.
Any help is highly appreciated!
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.