On Mon, May 14, 2012 at 04:11:20PM +0200, Michael Hampicke wrote:
> If I remember correctly, EncFS is not a file system on it's own, it's
> more like an addon to any other file system.
> So maybe the problem is not with EncFS, but the underlaying file system.
> A wild guess would be that the underlaying filesystem of your EncFS
> partition is ext2/3/4 and has run out of inodes? You can check the inode
> count with 'df -i'
> This happend to me once, but I cannot remember if the file system then
> was mounted readonly or there were 'out-of-space' error messages.
It's a reiserfs, and df -i shows zeroes; I had never given any thought
to reiserfs and inodes. Interesting.
> If that does not help, try to fsck your EncFS partition. Unmount first.
I may try that later. What puzzles me is that remounting without
reboot still came up read-only, even tho it had been read-write for 20
hours, and reboot came up read-write.
I wonder if some timeout feature was added to encfs or fuser, such that
if there is no activity for a certain time, it becomes read-only. I
didn't see any such change in any release notes. My little screen
jobis still creating files every minute, and will defeat any such
timeout, so there's something else to investigate later.
encfs was last emerged 14 March. fuser was last emerged 23 Apr. I
have rebooted several times since then, so I don't think either of
them had any sudden surprises left.
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@... GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o