From: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: attempt to access beyond end of device
Date: Thu, 27 Mar 2014 13:39:18 +0100 [thread overview]
Message-ID: <20140327123918.GH30294@wloczykij> (raw)
In-Reply-To: <1395739090.2197.11.camel@slavad-CELSIUS-H720>
[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]
On Tue, Mar 25, 2014 at 01:18:10PM +0400, Vyacheslav Dubeyko wrote:
> On Mon, 2014-03-24 at 21:49 +0100, Piotr Szymaniak wrote:
>
> > That was some time ago, so I'm unable to answer this question. But
> > nilfs-tune shows 4KB blocks:
> >
> > ~ # nilfs-tune -l /dev/sdf3
> > nilfs-tune 2.1.6
> > Filesystem volume name: (none)
> > Filesystem UUID: 53760664-f9ed-4c8d-af42-c6ee2f16d956
> > Filesystem magic number: 0x3434
> > Filesystem revision #: 2.0
> > Filesystem features: (none)
> > Filesystem state: invalid or mounted,error
> > Filesystem OS type: Linux
> > Block size: 4096
> > Filesystem created: Fri Aug 3 08:37:06 2012
>
> I suspect that you used this NILFS2 volume with kernel version that it
> was trouble with segments creation. So, you can have volume corruption
> because of this bug that it was fixed.
>
> (1) What Linux kernel version do use currently?
I think it was 3.6.y or 3.10.y
> (2) How long did you use old kernel versions?
I suppose at least since 2012-10.08 [1] as this is the same Raspberry Pi
and, afair, the same fs. So it was 3.2.27 and then some of (some of them
was unstable) 3.{6,10,11}.y
> (3) What workloads did you use for this volume?
It was almost idle except once a day or two accepting backup from
another machine (but that was kept on external drive/fs).
> (4) Had you situations of simultaneous working of several threads with
> intensive operations with volume (for example, simultaneous compilation
> and checking for updates)?
Could be, but compilation was made on external drive. nilfs holds the
rootfs and almost nothing more.
[1] http://marc.info/?l=linux-nilfs&m=134973563927736&w=2
Piotr Szymaniak.
--
Czekajcie, czekajcie. Ktos cos do mnie mowil, ale nie wiem kto i nie
wiem co.
-- Rafal Solecki
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-27 12:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 7:13 attempt to access beyond end of device Piotr Szymaniak
2014-03-24 7:37 ` Vyacheslav Dubeyko
2014-03-24 20:49 ` Piotr Szymaniak
2014-03-25 9:18 ` Vyacheslav Dubeyko
2014-03-27 12:39 ` Piotr Szymaniak [this message]
2014-03-29 14:49 ` Vyacheslav Dubeyko
2014-03-24 22:31 ` Piotr Szymaniak
-- strict thread matches above, loose matches on Subject: below --
2010-04-26 20:20 Re: Attempt to Access Beyond End of Device willis
2010-04-26 20:54 ` Eric Sandeen
2007-09-10 13:59 Federico Sevilla III
2007-09-10 14:44 ` Justin Piszcz
2007-09-10 14:59 ` Federico Sevilla III
2007-09-10 15:45 ` Justin Piszcz
2007-09-10 15:51 ` Federico Sevilla III
2007-09-10 15:47 ` Eric Sandeen
2007-09-10 15:54 ` Federico Sevilla III
2007-09-10 16:28 ` Eric Sandeen
[not found] ` <cc7060690709111208u3e0842f9rd6edff16539b8a28@mail.gmail.com>
2007-09-12 5:17 ` Federico Sevilla III
2006-12-05 14:01 attempt to access beyond end of device Koen Vereeken
2006-01-19 12:02 Handling of read errors in raid6 Filipe Maia
2006-01-19 20:39 ` attempt to access beyond end of device PFC
2004-04-13 10:03 Luca Ferrari
2004-04-13 10:41 ` Thomas Steudten
2004-04-13 11:08 ` Luca Ferrari
2004-04-13 11:20 ` Thomas Steudten
2004-04-13 11:45 ` Luca Ferrari
2004-04-13 12:44 ` Thomas Steudten
2004-04-13 12:53 ` Luca Ferrari
2002-12-06 5:21 Justin Pryzby
2002-12-05 18:54 Justin Pryzby
2000-12-07 15:56 Jan Niehusmann
2000-12-07 16:34 ` Andries Brouwer
2000-12-07 17:10 ` John Kennedy
2000-11-24 9:02 Janek
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=20140327123918.GH30294@wloczykij \
--to=szarpaj-tbom9ca2r9grdjvtcaxf/a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.