Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@adurom.com>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Filesystem corruption with 2.6.36-rc1-wl+ and ecryptfs
Date: Thu, 26 Aug 2010 09:46:13 +0300	[thread overview]
Message-ID: <87k4nd98i2.fsf@purkki.adurom.net> (raw)
In-Reply-To: <87tymt9iex.fsf@purkki.adurom.net> (Kalle Valo's message of "Tue\, 17 Aug 2010 21\:57\:10 +0300")

Kalle Valo <kvalo@adurom.com> writes:

> I just installed my first 2.6.36 kernel, 2.6.36-rc1-wl+ from
> wireless-testing, and immeadialy (during first boot) got major
> corruption in the filesystem. For example, gnome lost it's settings,
> ~/.ssh was empty etc. Now, with an older kernel, my directory
> structure has duplicate entries, like this:
>
> $ ls -ald D*
> drwxr-xr-x 2 kvalo kvalo 4096 2010-08-17 19:21 Desktop/
> drwxr-xr-x 2 kvalo kvalo 4096 2010-08-17 19:21 Desktop/
> drwxr-xr-x 2 kvalo kvalo 4096 2010-08-17 19:21 Documents/
> drwxr-xr-x 2 kvalo kvalo 4096 2010-08-17 19:21 Documents/
> drwxr-xr-x 2 kvalo kvalo 4096 2010-08-17 19:21 Downloads/
> drwxr-xr-x 2 kvalo kvalo 4096 2010-08-17 19:21 Downloads/
>
> I'm using ecryptfs and that's my major suspect for the corruption, but
> naturally I can't be sure because I'm just guessing here. 

(For the archives)

It was ecryptfs, bug report here:

https://bugs.launchpad.net/ecryptfs/+bug/623087

And fix here:

http://git.kernel.org/?p=linux/kernel/git/ecryptfs/ecryptfs-2.6.git;a=commitdiff;h=b4ef26e06ce0c4877bd5a736b0dfb318a4fb9002

-- 
Kalle Valo

      reply	other threads:[~2010-08-26  6:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 18:57 Filesystem corruption with 2.6.36-rc1-wl+ and ecryptfs Kalle Valo
2010-08-26  6:46 ` Kalle Valo [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=87k4nd98i2.fsf@purkki.adurom.net \
    --to=kvalo@adurom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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