git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Help with a possibly corrupt repo

From
Dmitry Potapov <dpotapov@gmail.com>
Date
May 21, 2010, 02:59 UTC
Message-ID
<20100521025954.GA3005@dpotapov.dyndns.org>
In-Reply-To
<AANLkTikSo8hTPXG8kGgCLOul6wp8THobUW_rSni4D6YC@mail.gmail.com>
On Thu, May 20, 2010 at 07:57:30AM -0700, Jonathan Leto wrote:
Show 13 quoted lines
> 
> 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
Previous: Jonathan Leto
Message 6 of 6 in “Help with a possibly corrupt repo”
  1. Jonathan LetoMay 10, 2010
  2. Dmitry PotapovMay 10, 2010
  3. Jonathan LetoMay 10, 2010
  4. Dmitry PotapovMay 10, 2010
  5. Jonathan LetoMay 20, 2010
  6. Dmitry PotapovMay 21, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.