NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Volume suddenly read-only
All of a sudden and out of nowhere, my volume has become read-only. The system does not show any errors and no disk malfunction. What the hell? I'm updating all my backups now, but what should I do ...
Ok, this is getting more and more difficult to pinpoint. Mac clients can open every file. Windows PCs cannot.
And now it's back to Read-Only mode. What a nightmare.
I, too have a volume that went read-only. A reboot clears it till a write operation occurs, then it goes read-only again. Interrestingly, the BTRFS readonly flag is set to false.
I happen to know what caused it on mine. The volume is in an EDA500 equivalent eSATA chassis and the cable came loose (it's the older shallow kind, not the newer, deeper one). Though the connection is OK now, the damage has apparently been done. Since this volume is fully backed up and consists of archival data rarely accessed, I decided to try a few things. But it sounds like you may not have tiime to wait for any answers I find.
I thought a scrub should fix the issue, so I started one. It self-aborted after 4 minutes. But initiating a scrub from the GUI also initiates a re-sync, and I have a few hours left for that to complete. Note that the GUI still says it's scrubbing, but SSH tells a different story. That the re-sync process seems to be doing fine tells me that the eSATA connection is now OK. But re-sync on an eSATA volume is even slower than a normal one, and so I wait.
Once the re-sync completes, I'm going to try a scrub from SSH so it won't also do another re-sync. If it then works, maybe the re-sync really was needed. If it still doesn't work, then I wasted a lot of time when I could have been destroying the volume, re-creating it, and restoring data from backup. While StephenB suggests a fctopry default, that's not the appropriate action for an external volume, but may be the only total solution for a single chassis system to insure the OS and swap partitions also don't have issues. But after all this, I'll know, and I can share my experience.
Re-sync completed and re-try at scrub self-aborted after 38 seconds. No reason given, no errors reported. So a little Googling suggested I start with the -B flag so it doesn't background it, and it then reported it aborted due to read-only file system. Which is odd, because btrfs property get /eda2 (my volume is eda2) returns ro=false.and the same is true of both sub-volumes. So I have more to learn about how a BTRFS filesystem is marked read-only.
All remaining tools appear to only work on an unmounted filesystem, and ReadyNASOS doesn't seem to want me to do that, so it's destroy and re-build for me.
But in my Googling, I did learn that a too-full volume can lead to it becoming read-only.. Could that be your issue? But that, of course, puts you in a catch-22, since you can't delete files from a too-full read-only volume. And doing a full restore from backup is going to put you right back where you were (or close, there may be a better data/metadata division that gets you by for a while).
Not it in my case. More than 70% free space. The problem arose one hour after deleting the LUN. Can quite put my finger on the cause of the problem.
Thank you very much for your input. In my case, I believe the file system was corrupted somehow during the deletion of the iSCSI LUN. It shouldn't have, there is no reason for it.
Unfortunately I don't have time to run test or even study the subject. I have to get this up and running as we have 45 employees depending on files in here. I schedule downtime for today and have to get this thing working again, so a system reset and restore will be faster (relatively, I have to restore 3 TB of data through USB which will take more than 10 hours).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
