linux-kernel - Re: Unable to create the previously deleted snapshot or subvolume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20090310162009.GA31499@merfinllc.com>
Date:	Tue, 10 Mar 2009 09:20:09 -0700
From:	Aaron Straus <aaron@...finllc.com>
To:	Siddhartha Swaroop <siddhartha.swaroop@...enturtles.in>
Cc:	linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org
Subject: Re: Unable to create the previously deleted snapshot or subvolume

Hi Siddhartha,

On Mar 10 02:42 PM, Siddhartha Swaroop wrote:
> So from about test case the problem I faced is when ever I try to
> create a snapshot or subvolume of same name which previously deleted
> it says file exists.But when I do "$ ls " that file will not be
> present in that directory.  But once in a while am able to create it
> as u can see in the about test steps  7,8,9.

Thanks.  That patch is certainly dangerous and meant more as a request
for help!  :)

That said, the most important thing I still don't understand is the tree
root forward and back refs.  

In particular I don't think BTRFS is adding all the forward and back
refs in the snapshot of snapshot case.

The will make snapshot deletion difficult because one cannot tell if the
tree root is still being referenced by another tree root (or not)...

Anyway, I think that's still the first thing to be cleaned up.

				Regards,
				=a=

-- 
===================
Aaron Straus
aaron@...finllc.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/