From: Goffredo Baroncelli <kreijack@libero.it>
To: linux-btrfs@vger.kernel.org
Subject: BUG: Link from sub volume, then remove the subvolume -> wrong link
Date: Fri, 11 Dec 2009 20:54:25 +0100 [thread overview]
Message-ID: <200912112054.25986.kreijack@libero.it> (raw)
Hi all
when I tried to reproduce the bug highlighted by Andrew, I discovered another
bug. When I link a file from a subvolume to another, then remove the subvolume
I got a wrong link: in my test an *hard* link becomes a *soft* link !!!!
Steps to reproduce the bug:
root@venice:/tmp/test# sudo btrfsctl -S subvol2 .
operation complete
Btrfs Btrfs v0.19
root@venice:/tmp/test# echo 123 >>subvol2/myfile
root@venice:/tmp/test# ln subvol2/myfile .
root@venice:/tmp/test# ls -l . subvol2/
.:
total 4
-rw-r--r-- 2 root root 4 2009-12-11 20:40 myfile
drwx------ 1 root root 12 2009-12-11 20:40 subvol2
subvol2/:
total 4
-rw-r--r-- 2 root root 4 2009-12-11 20:40 myfile
root@venice:/tmp/test# btrfsctl -D subvol2 .
operation complete
Btrfs Btrfs v0.19
root@venice:/tmp/test# ls -l
total 0
lrwxrwxrwx 1 root root 3 2009-11-22 10:56 myfile -> lib
Now myfile is a soft link instead to a hard link!!!! Moreover the soft link is
to an incorrect target ( 1) lib doesn't exist, 2) in any case is not the right
target).
BR
Goffredo
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
next reply other threads:[~2009-12-11 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 19:54 Goffredo Baroncelli [this message]
2009-12-12 0:24 ` BUG: Link from sub volume, then remove the subvolume -> wrong link TARUISI Hiroaki
2009-12-12 13:54 ` Goffredo Baroncelli
2009-12-12 18:39 ` Andy Lutomirski
2009-12-13 23:42 ` TARUISI Hiroaki
2009-12-14 18:43 ` Andrew Lutomirski
2009-12-15 0:15 ` TARUISI Hiroaki
2009-12-15 4:04 ` Andy Lutomirski
2009-12-15 17:31 ` David Nicol
2009-12-17 0:00 ` TARUISI Hiroaki
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=200912112054.25986.kreijack@libero.it \
--to=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.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