Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	lwojcicki-V+nj596LuoKHKKo6LODCOg@public.gmane.org
Subject: Re: nilfs_cleanerd problem
Date: Thu, 03 Dec 2009 18:56:55 +0900 (JST)	[thread overview]
Message-ID: <20091203.185655.55999146.ryusuke@osrg.net> (raw)
In-Reply-To: <1259830135.10111.8.camel@Stanowisko-25>

Hi,
On Thu, 03 Dec 2009 09:48:55 +0100, Lukasz Wojcicki <lwojcicki-V+nj596LuoKHKKo6LODCOg@public.gmane.org> wrote:
> Too late.
> I reformat SSD disk to FAT32 and format to NILFS2 again. Now it work
> correctly.

No, no. I suspect some kind of media error happened.  My intention is
just reading the block device for narrowing down the cause.  So, it's
independent with which filesystem is written on the device.

> When I've got another error yesterday too. I've got ETIME error (from
> linux kernel) while transferring large file (log) from SSD disk. This
> situation was place, when nilfs_cleanerd was running and I execute
> lscp . Then (after long time) nilfs_cleanerd was stopped .

Seems that the ETIME error comes from the device layer because nilfs
doesn't return it.  I suspect cleanerd actually caused the issue.  But
it seems to me that cleanerd degraded or overloaded your device.

So, I thought we first should test the device itself.

Regards,
Ryusuke Konishi

  reply	other threads:[~2009-12-03  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02  8:52 nilfs_cleanerd problem Łukasz Wójcicki
2009-12-02 16:06 ` Ryusuke Konishi
     [not found]   ` <20091203.010653.90356741.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-12-02 16:17     ` Ryusuke Konishi
2009-12-03  8:48     ` Łukasz Wójcicki
2009-12-03  9:56       ` Ryusuke Konishi [this message]
     [not found]         ` <20091203.185655.55999146.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-12-11  6:22           ` Łukasz Wójcicki
2009-12-11  7:04             ` Łukasz Wójcicki

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=20091203.185655.55999146.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=lwojcicki-V+nj596LuoKHKKo6LODCOg@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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