I ended up repairing the filesystem. Looks like I lost a bunch of data,
but at least the corruption is clear. Luckily I have backups of most of the
information lost.
Thanks everyone for your help in figuring this out.
Bobby
On Tue, Apr 20, 2010 at 12:06 PM, J. Bobby Lopez <j...@jbldata.com> wrote:
> Yep, it looks like there are a lot of problems at the filesystem level. I
> wonder if I should use fsck to try and fix them?
>
> Here's what the errors look like:
> =============================================
> BZR-REPOS-USB has been mounted 35 times without being checked, check
> forced.
> Pass 1: Checking inodes, blocks, and sizes
> Inode 306561 is in use, but has dtime set. Fix? no
>
> Inode 306561 has imagic flag set. Clear? no
>
> Inode 306561 has a extra size (57714) which is invalid
> Fix? no
>
> Inode 306562 has EXTENTS_FL flag set on filesystem without extents support.
> Clear? no
>
> Inode 306562 is in use, but has dtime set. Fix? no
>
> Inode 306562 has imagic flag set. Clear? no
>
> Inode 306562 has a extra size (37904) which is invalid
> Fix? no
>
> Inode 306562 has compression flag set on filesystem without compression
> support. Clear? no
>
> Inode 306562 has INDEX_FL flag set but is not a directory.
> Clear HTree index? no
>
> HTREE directory inode 306562 has an invalid root node.
> Clear HTree index? no
>
> Inode 306562, i_blocks is 71997614704888, should be 0. Fix? no
>
> Inode 306563 has EXTENTS_FL flag set on filesystem without extents support.
> Clear? no
>
> Inode 306563 is in use, but has dtime set. Fix? no
>
> Inode 306563 has imagic flag set. Clear? no
>
> Inode 306563 has a extra size (3654) which is invalid
> Fix? no
>
> Inode 306563 has INDEX_FL flag set but is not a directory.
> Clear HTree index? no
>
> HTREE directory inode 306563 has an invalid root node.
> Clear HTree index? no
>
> Inode 306563, i_blocks is 265262120981675, should be 0. Fix? no
>
> Inode 306564 is in use, but has dtime set. Fix? no
>
> Inode 306564 has imagic flag set. Clear? no
>
> Inode 306564 has a extra size (19106) which is invalid
> Fix? no
>
> Inode 306565 is in use, but has dtime set. Fix? no
> ....
> =============================================
>
>
> And finally at the bottom....
>
> =============================================
> Inode 309638 has INDEX_FL flag set but is not a directory.
> Clear HTree index? no
>
> HTREE directory inode 309638 has an invalid root node.
> Clear HTree index? no
>
> Inode 309638, i_size is 6322120545066263974, should be 0. Fix? no
>
> Inode 309638, i_blocks is 183996110528189, should be 0. Fix? no
>
> Inode 306571 has compression flag set on filesystem without compression
> support. Clear? no
>
> Inode 306571 has illegal block(s). Clear? no
>
> Illegal block #0 (1860635212) in inode 306571. IGNORED.
> Illegal block #1 (2851183781) in inode 306571. IGNORED.
> Illegal block #2 (3628887291) in inode 306571. IGNORED.
> Illegal block #3 (771166816) in inode 306571. IGNORED.
> Illegal block #4 (3873215808) in inode 306571. IGNORED.
> Illegal block #5 (2037458758) in inode 306571. IGNORED.
> Illegal block #6 (833641894) in inode 306571. IGNORED.
> Illegal block #7 (2372989805) in inode 306571. IGNORED.
> Illegal block #8 (2497385137) in inode 306571. IGNORED.
> Illegal block #9 (3581160034) in inode 306571. IGNORED.
> Illegal block #10 (3814544214) in inode 306571. IGNORED.
> Too many illegal blocks in inode 306571.
> Clear inode? no
>
> Suppress messages? no
>
> Illegal block #11 (3313708609) in inode 306571. IGNORED.
> Illegal block #-1 (3942679233) in inode 306571. IGNORED.
> Illegal block #-2 (1977906426) in inode 306571. IGNORED.
> Illegal block #-3 (191716658) in inode 306571. IGNORED.
> Error while iterating over blocks in inode 306571: Illegal triply indirect
> block found
> =============================================
>
>
> I'm guessing I'm out of luck?
>
>
>
>
>
> On Tue, Apr 20, 2010 at 11:55 AM, <si...@mungewell.org> wrote:
>
>> > Nope, I get the following error when I try to cd into the directory:
>> >
>> > $ cd logmate.repo
>> > bash: cd: logmate.repo: Input/output error
>> >
>> > I can't even seem to delete the directory :(
>> >
>>
>> So you should have 2 mount points, one for vfat (???) USB stick and one
>> for the EncFS/Fuse overlay.
>>
>> In the USB one can you see the files/directories. These should be visible
>> albeit encrypted with funny names, however meta-data will probably be the
>> same(ish) depending on the encfs options.
>>
>> If you can not access the underlying files, I suggest working to recover
>> those with fsck/etc.
>>
>> Also check the permissions on the files/directories to ensure that they
>> are accessible by the user who is doing the fuse mount.
>>
>> Simon
>>
>>
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Encfs-users mailing list
Encfs-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/encfs-users
