Drobo

Linux EXT3 mount changes to read-only

Drobo USB connected to a SUSE Linux Dell Server with EXT3 file system. Mounted read-write works no problem for a while and it will then just flip over to a read-only mount. I can’t find a reason for this behavior.

Has anyone else experienced this?

Thanks!

Never seen it with a Drobo, I have seen similar behaviour in the case of i/o errors on random devices.
Did you check your dmesg and system log?

how old is your suse version?

I have been having a similar problem for the past few weeks. My drobo is set to remount as Read Only when disk errors are encountered.

If I run fsck.ext3, then a bunch of errors are found, and need to be manually corrected. Once I do this, the drobo works find for another 3 to 5 days, then gets another disk error, and I need to repeat the process again.

Not sure why the file system is becoming corrupted though. The drobo has not been turned off, and I can not see anything related in syslog or dmesg.

This may the the cause of your system turning to RO.

Anyone have any ideas why the file system suffers corruption on such a regular basis?

I can’t explain why but I can concur I am seeing the same behaviour with a DroboPro - 3x1TB drives formatted as hfsplus on an Ubuntu system.
Problem has worsened to the point where fsck now can’t repair everything.

sudo fsck /dev/sdb2

fsck from util-linux-ng 2.16
** /dev/sdb2
** Checking HFS Plus volume.
** Checking Extents Overflow file.
Invalid index key
(3, 1)
** Repairing volume.
** Rechecking volume.
** Checking HFS Plus volume.
** Checking Extents Overflow file.
Invalid index key
(3, 1)
** Repairing volume.
** Rechecking volume.
** Checking HFS Plus volume.
** Checking Extents Overflow file.
Invalid index key
(3, 1)
** Repairing volume.
** Rechecking volume.
** Checking HFS Plus volume.
** Checking Extents Overflow file.
Invalid index key
(3, 1)
** The volume Drobo could not be repaired after 3 attempts.

I am thinking of trying NTFS instead. If that fails, I will be returning the device as only 2GB LUN’s for ext3 isn’t enough (heck - i could simply buy 2TB drives…)

iohouse: how big is are your LUNs?

mine (1) LUN has been stable for over a year, It is 2 TiB ext3.