From mboxrd@z Thu Jan 1 00:00:00 1970 From: C Anthony Risinger Subject: Re: default subvolume abilities/restrictions Date: Sat, 12 Jun 2010 20:06:34 -0500 Message-ID: References: <29213501.290601274270192630.JavaMail.defaultUser@defaultHost> <20100613002252.GA12170@arch.davidb.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 To: linux-btrfs@vger.kernel.org Return-path: In-Reply-To: <20100613002252.GA12170@arch.davidb.org> List-ID: On Sat, Jun 12, 2010 at 7:22 PM, David Brown wrote: > On Sat, Jun 12, 2010 at 06:06:23PM -0500, C Anthony Risinger wrote: > >>> # btrfs subvolume create new_root >>> # mv . new_root/old_root > >> can i at least get confirmation that the above is possible? > > I've had no problem with > > =A0# btrfs subvolume snapshot . new_root > =A0# mkdir old_root > =A0# mv * old_root > =A0# rm -rf old_root > > Make sure the 'mv' fails fo move new_root, and I'd look at the > new_root before removing everything. > > David heh, yeah i as i was writing the last email i realized that all i really wanted was to: # mv * new_root for some reason i was convinced that i must snapshot the old_root (.) to new_root... and then remove the erroneous stuff from old_root (.). thus a way to "parent" the default subvol (old_root/.) seemed a better solution... but alas, a snapshot isn't necessary. i can create an empty subvol "new_root", and then "mv * new_root". i don't know how that escaped me :-), sorry for all the noise. however, there probably is a legitimate use case for wanting to replace the default subvolume, but this isn't it. C Anthony -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html