Ecryptfs is not made for volumes. You make a folder that holds your encrypted files. Then you mount it at another location that's in the clear. Perhaps your looking for full-disk encryption instead of filesystem-level encryption. Here's a note from the btrfs wikipedia page: The current recommendation for encryption with btrfs is to use a full-disk encryption mechanism such as dm-crypt or LUKS on the underlying devices, and to create the btrfs filesystem on top of that layer (and that if a RAID is to be used with encryption, encrypting a dm-raid device or a hardware-RAID device gives much faster disk performance than dm-crypt overlaid by btrfs's own filesystem-level RAID features) B. J. On Mon, Dec 3, 2012 at 9:01 AM, <CACook@xxxxxxxxxxxxxxx> wrote: > On Saturday, December 01, 2012 01:06:59 PM CACook@xxxxxxxxxxxxxxx wrote: >> >> My backups server has a 4 drive BTRFS array (2TB each), and is mounted on /media/backups. Under that are BTRFS subvolumes named for the LAN systems they back up, such as hex, droog, etc. Also under backups is where the snapshots are made, such as hex-snap-2012-10-15, droog-snap-2012-10-15, and so on. >> >> So where can I encrypt? Do I have to go in to each subvolume and make private directories for each of those subdirs like bin, etc, lib, and so on? If so, how would I update the new snapshots which are created, for encryption? >> >> It doesn't seem possible to encrypt a BTRFS subvolume, and certainly not an array? > > Anyone here? > > -- > To unsubscribe from this list: send the line "unsubscribe ecryptfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
