20160416 disk read-only issue

• ext3_lookup: unlinked inode 8441457 in dir #8441317

 Just an update for anyone who sees this problem in the future.

The apparent cause of this issue was that the array was initializing during filesystem creation. Even though everything in the Adaptec documentation states "you can use the logical drive immediately", this does not appear to be the case. We waited until the array was initialized, then created a new filesystem on the partition. This filesystem passed all the fscks I've thrown at it so far and we've written several terrabytes of data without issue (knock on wood).

in sum: do not create filesystems until the array has finished initializing, no matter what the documentation says. YMMV, etc etc.

References

http://ssms.cs2c.com.cn/otrs/pc.pl?Action=PublicFAQZoom;CategoryID=14;ItemID=3756

A Little ‘file’ Black Magic:

(Bonus) You can detect Journal issues with the ‘file’ command if you do not have any other tools at your disposal.

# file -sL /dev/sdb1
/dev/sdb1: Linux rev 1.0 ext3 filesystem data (needs journal recovery)