Linux NILFS development
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven-KaDOiPu9UxWEi8DpZVb4nw@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] nilfs-utils: Work around uncleanable full filesystem
Date: Tue, 15 Jan 2013 16:17:17 +0100	[thread overview]
Message-ID: <2312125.8JVqXAGppa@bentobox> (raw)
In-Reply-To: <1358258241.2094.9.camel@slavad-ubuntu>

[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

On Tuesday 15 January 2013 17:57:21 Vyacheslav Dubeyko wrote:
> Could you share more details about your environment? What version of
> nilfs-utils do you use?
> 
> Maybe do you have some NILFS2-related error messages in your system log?
> 
> Or, maybe, reproducing path is more complex as you described?

System running Debian Wheezy (amd64) with linux 3.2.35-2 and nilfs-tools 
2.1.4-1. The nilfs partition is a secondary partition on a CFCard and is not 
used in normal situations. There are different processes running in the 
background... for example ntpd. There are no interesting infos in the system 
log (unless you are interested in nilfs_cleanerd output saying nothing else 
than "pause"/"sleep"/"0 segments selected to be cleaned"/...).

Following way is a good way to force a similar problem (this is not the way I 
produced it the first time, but it is a possible scenario):

$ cd /nilfs/
$ ntpdate-debian
$ date -s @`date +'%s'|awk '{ print $1+9000}'`
$ for i in `seq 0 300`; do dd if=/dev/zero of=foo$i count=22528; done
$ sleep 360
$ ntpdate-debian
$ touch asd
$ rm *
$ date -s @`date +'%s'|awk '{ print $1+10000}'`
$ mount -o remount /nilfs/

It is a little bit harsh, but a similar thing can easily happen in real world 
with non-monotonic clocks (but the jumps are usually a little smaller).

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-01-15 15:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 15:54 [PATCH] nilfs-utils: Work around uncleanable full filesystem Sven Eckelmann
     [not found] ` <1358178899-26347-1-git-send-email-sven-KaDOiPu9UxWEi8DpZVb4nw@public.gmane.org>
2013-01-14 19:49   ` Vyacheslav Dubeyko
     [not found]     ` <37A149BD-4D8E-4C55-9301-428034C5B9DA-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-01-14 18:55       ` Sven Eckelmann
2013-01-15  7:14   ` Vyacheslav Dubeyko
2013-01-15  8:34     ` Sven Eckelmann
2013-01-15 10:43     ` Ryusuke Konishi
     [not found]       ` <201301151043.AA04492-ZdTO5nnmHvkOizVVqyxoihMFgDP4sedm@public.gmane.org>
2013-01-15 13:48         ` Vyacheslav Dubeyko
2013-01-15 13:57   ` Vyacheslav Dubeyko
2013-01-15 15:17     ` Sven Eckelmann [this message]
2013-01-17  7:57       ` Vyacheslav Dubeyko
2013-01-17  8:32         ` Sven Eckelmann
2013-01-17  9:19           ` Vyacheslav Dubeyko
2013-01-18  7:04           ` Vyacheslav Dubeyko
2013-01-18  6:17         ` Vyacheslav Dubeyko

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=2312125.8JVqXAGppa@bentobox \
    --to=sven-kadoipu9uxwei8dpzvb4nw@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=slava-yeENwD64cLxBDgjK7y7TUQ@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