LKML Archive on
help / color / mirror / Atom feed
From: Pavel Machek <>
To: Sergey Smirnov <>
Subject: Re: HELP!!! SD and suspend damage i-node.
Date: Fri, 23 Mar 2007 22:58:21 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


> I use kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750 (PXA255).
> After suspend/resume filesystem stay clean. But some i-nodes become broken.
> Some files looks like block device or pipe with strange permissions, owner etc.
> I'm sure that there is no bad blocks on SD.
> I'll send any additional information. Just say me what you need to help me.
> I had i lot of tries. Apply patches, remove its, change fstype etc.
> output of fsck -f

How repeatable is the corruption? I have c3000 here, and it corrupts
memory during system, say during one in 5 suspends. Longer suspends
seem to lead to 'more' corruption.

It did not damage my filesystem, yet.

Do you use bluetooth?
(cesky, pictures)

  parent reply	other threads:[~2007-03-24  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 12:35 Sergey Smirnov
2007-03-22 21:55 ` Rafael J. Wysocki
2007-03-23 11:25   ` Sergey Smirnov
2007-03-23 22:38     ` Rafael J. Wysocki
2007-03-23 22:58 ` Pavel Machek [this message]
2007-03-26  6:48   ` Sergey Smirnov
2007-03-27 12:08     ` Pavel Machek

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: HELP'\!''\!''\!' SD and suspend damage i-node.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).