From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from plane.gmane.org ([80.91.229.3]:54179 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751434AbbBEWte (ORCPT ); Thu, 5 Feb 2015 17:49:34 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YJVEq-00070c-1w for linux-btrfs@vger.kernel.org; Thu, 05 Feb 2015 23:49:32 +0100 Received: from moeller.plus.com ([81.174.172.105]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Feb 2015 23:49:32 +0100 Received: from huaraz by moeller.plus.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Feb 2015 23:49:32 +0100 To: linux-btrfs@vger.kernel.org From: "Markus Moeller" Subject: Re: Btrfs subvolume question Date: Thu, 5 Feb 2015 22:49:18 -0000 Message-ID: References: <54D2E62E.7080208@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original In-Reply-To: Sender: linux-btrfs-owner@vger.kernel.org List-ID: It seems systemd creates the subvolumes. > cat /run/systemd/generator/local-fs.target.requires/var-opt.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Before=local-fs.target [Mount] What=/dev/disk/by-uuid/7a681ad4-5b82-4e78-9b20-1d719c89fe6f Where=/var/opt Type=btrfs Options=subvol=var/opt Markus "Chris Murphy" wrote in message news:CAJCQCtT1pSrFEU7Q0qspNkqzY9naDHxzzyE5y3fyqgZqqkT_vA@mail.gmail.com... On Thu, Feb 5, 2015 at 1:28 PM, Markus Moeller wrote: > Thank you for looking at this. I did post the fstab in the original > post. Yep! No aware for my observation skills on this thread... > Here it is again: Hmm, it's using UUIDs for the Btrfs volumes rather than using the VG/LV. If you use # lvs that'll show the LVM LV's. But Robert already got this figured out. > The only thing I intended was to separate /, /var, /opt, /usr and /boot > as > I was used to, to avoid for example /var/log filling up the root > filesystem > ( but now this fails :-( ) /var/log is on system_13.2/root_lv along with a bunch of other things. According to your first df though, this 5GB root_lv is far from full, not even 1/2 full. So I don't have a good explanation. Anyway, long term this layout has maintenance problems, I would start over. Backing up, restoring, even updating will pose problematic. -- Chris Murphy -- 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