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:
signature.asc
Description: Digital signature
