From: David Arendt <admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: silent random symbolic link corruption
Date: Sat, 31 Jan 2009 21:13:16 +0100 [thread overview]
Message-ID: <4984B0DC.6080905@prnet.org> (raw)
Hi,
After using nilfs2 for half a year now on data partitions without any
problems, I wanted to try it for the root partition. This way I
discovered a silent random symbolic link corruption problem.
Versions:
latest nilfs2 git module
kernel 2.6.28.2
tar 1.20
Step to reproduce it:
tar -xpf zz1.tar (where zz1.tar is a tar file containing many symbolic
links (in my case a directory containing 2 root filesystems for remote
booting)
On untar some symbolic links are missing and 0 byte files are existing
instead.
I repeated the test 3 times on a freshly formated nilfs2 partition and
always had other links missing.
I am currently trying to bzip2 the big tar file and untar this one in
order to verify if there are no timing issues and will report back when
this test is finished.
Could you please look into this ?
Thanks in advance
Bye,
David Arendt
next reply other threads:[~2009-01-31 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 20:13 David Arendt [this message]
[not found] ` <4984B0DC.6080905-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2009-01-31 20:48 ` silent random symbolic link corruption David Arendt
2009-01-31 23:21 ` David Arendt
[not found] ` <4984DCF3.8030302-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2009-02-02 2:42 ` Ryusuke Konishi
[not found] ` <20090202.114209.59790430.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-02-02 17:32 ` David Arendt
[not found] ` <49872E1E.4090209-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2009-02-02 21:01 ` David Arendt
[not found] ` <49875F16.7060107-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2009-03-08 6:37 ` Ryusuke Konishi
[not found] ` <20090308.153730.64866441.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-08 13:07 ` Ryusuke Konishi
2009-03-08 15:45 ` Ryusuke Konishi
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=4984B0DC.6080905@prnet.org \
--to=admin-/lhds3kc8bfytjvyw6ydsg@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 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.