From: Dmitry Potapov <dpotapov@gmail.com>
To: Jonathan Leto <jaleto@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Help with a possibly corrupt repo
Date: Fri, 21 May 2010 06:59:54 +0400 [thread overview]
Message-ID: <20100521025954.GA3005@dpotapov.dyndns.org> (raw)
In-Reply-To: <AANLkTikSo8hTPXG8kGgCLOul6wp8THobUW_rSni4D6YC@mail.gmail.com>
On Thu, May 20, 2010 at 07:57:30AM -0700, Jonathan Leto wrote:
>
> I ran into this corruption issue using ecryptfs with an ext4
> filesystem (on a local SSD drive) on Ubuntu 9.10.
> to coincide with getting these errors in my dmesg output:
>
> [12773.772426] ecryptfs_decrypt_page: Error attempting to read lower
> page; rc = [-22]
> [12773.772431] ecryptfs_readpage: Error decrypting page; rc = [-22]
> [12796.061574] ecryptfs_read_lower: octets_read = [-4]; expected [4096]
> [12796.061584] ecryptfs_read_and_validate_header_region: Error reading
> header region; rc = [-22]
>
> I am lead to believe that ecryptfs+ext4 is not yet production-ready,
Sounds like this bug:
https://bugs.launchpad.net/ecryptfs/+bug/509180
and maybe related to this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/490005
I don't think it is caused by combination of ecryptfs+ext4. I have seen
a similar bug report for ecryptfs+ext3 as well. In fact, a lot of bug
fixes were merged for ecryptfs during 2.6.34 development cycle.
Perhaps, those fixes were also back ported to 2.6.32, but Ubuntu 9.10
has 2.6.31, so it does not have them, and without them, it looks like
a beta-quality filesystem. So, make sure you have regular backups!
Dmitry
prev parent reply other threads:[~2010-05-21 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 19:37 Help with a possibly corrupt repo Jonathan Leto
2010-05-10 20:17 ` Dmitry Potapov
2010-05-10 21:05 ` Jonathan Leto
2010-05-10 21:28 ` Dmitry Potapov
2010-05-20 14:57 ` Jonathan Leto
2010-05-21 2:59 ` Dmitry Potapov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100521025954.GA3005@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=jaleto@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).