Originally posted by GreyGeek
View Post
Code:
vdir /mnt/@home/jerry
VINNY
-
vdir is listing jerry as the directory in /mnt/@home and /home ,,,,,,, what if ,,,,,,?
VINNYi7 4core HT 8MB L3 2.9GHz
16GB RAM
Nvidia GTX 860M 4GB RAM 1152 cuda cores
-
As you would suspect, populated ...:Originally posted by vinnywright View Post
But, the /home under @ is empty!root@jerry-Aspire-7739:~# vdir /mnt/@home/jerry
total 1140
-rw-rw-r-- 1 jerry jerry 311453 Apr 5 10:27 Apt_from_Street.png
-rw-rw-r-- 1 jerry jerry 633782 Jan 1 2015 bookmarks-12-28-14.html
-rw-rw-r-- 1 jerry jerry 3032 Jul 5 18:09 btrfs_disection.txt
drwxr-xr-x 1 jerry jerry 20 Dec 31 2014 Desktop
drwxr-xr-x 1 jerry jerry 2276 Jul 5 18:31 Documents
drwxr-xr-x 1 jerry jerry 3438 Jul 4 13:51 Downloads
drwxrwxr-x 1 jerry jerry 118 Jun 3 21:07 FFT
...
I noticed this because the link giving the directions for conversion had the following:
root@jerry-Aspire-7739:~# vdir /mnt/@/home
total 0
root@jerry-Aspire-7739:~#
I created subvolume for /home in the same way:
# btrfs subvol create /mnt/rootfs/@home
Then moved /home to subvolume and created the mount point:
# mv home/* @home/
# rmdir home
# mkdir @/home
Then checked that all data are in the corresponding subvolumes:
...
I asked myself why he was creating @/home and putting nothing in it? Because Ubuntu is configured that way, and @/home is what @home is mounted to by fstab. When you mount the btrfs system using mount /dev./sdaX /mnt as root the @home subvolume isn't mounted to @/home, but @home/jerry has all of my account stuff in it.Last edited by GreyGeek; Jul 05, 2015, 09:01 PM."A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
– John F. Kennedy, February 26, 1962.Comment
-
Open it in Ark. For that particular file, Ark can't figure out what it is, and presents you with a dialog. Choose Raw CD image.Originally posted by Qqmike View PostComment
-
Actually, mine opened fine in ARK without choosing Raw CD Image.SteveRiley: Open it in Ark. For that particular file, Ark can't figure out what it is, and presents you with a dialog. Choose Raw CD image.
Did it with both:
debian-8.1.0-amd64-netinst
debian-live-8.1.0-amd64-kde-desktop
The former showing all sorts of grub and efi good stuff; the latter showing none of it, just its own isolinux for the CD booting (I assume).
Thanks.An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
About my Debian experiment and UEFI and Post #98 above,
https://www.kubuntuforums.net/showth...l=1#post375642
Where to get that nice, small, CD installer file that is "complete" and that has UEFI capablity?
As I had difficulty hanging on to it, I'll post it (thanks to SteveRiley for this clarification of installer files):
Network install from a minimal CD
https://www.debian.org/CD/netinst/
The general guidance is this (which maybe you can ignore):
http://cdimage.debian.org/debian-cd/8.1.0/amd64/iso-cd/
How to fix your UEFI booting after installing Debian?
I edited my Post #98 to include this, along with a link. Did so since Debian UEFI booting was a main focus of mine and so thought I should include a fix, others here seem to be serious about installing Debian, and others here are interested in getting into UEFI vs the older BIOS+MBR booting.An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
In my previous posting about JessieKDE and Btrfs I gave a link which showed how to convert a Debian Jessie EXT4 installation to Btrfs WITH Ubuntu's configuration. I tried it in a JessieKDE guest OS and it failed at the point where
btrfs subvol create /mnt/rootfs/@
with an "ioctl" error.
So, I reinstalled JessieKDE guest with two partions, a 15GB root and a 55GB home partition and played with snapshots to see how I could mimick the Ubunto technique.
The two btrfs root volumes, root, /, is on sda1 and /home is on sda2. Attempting to create a snapshot on sda1 from a subvolume on sda2 fails with a cross device error. Perhaps send and recieve would work.jerry@debian:~$ su -
Password:
root@debian:~# vdir /mnt
total 0
root@debian:~# mount /dev/sda2 /mnt
root@debian:~# vdir /mnt
total 0
drwxr-xr-x 1 jerry jerry 526 Jul 6 14:56 jerry
root@debian:~# ls -a /mnt
. .. jerry .snapshots
root@debian:~# vdir /mnt/.snapshots/
total 16
drwxr-xr-x 1 root root 30 Jul 6 14:48 home_snap
root@debian:~# vdir /mnt/.snapshots/home_snap/
total 0
drwxr-xr-x 1 jerry jerry 506 Jul 6 14:47 jerry
root@debian:~# vdir /mnt/.snapshots/home_snap/jerry/
total 0
drwxr-xr-x 1 jerry jerry 0 Jul 6 14:09 Desktop
drwxr-xr-x 1 jerry jerry 0 Jul 6 14:09 Documents
drwxr-xr-x 1 jerry jerry 0 Jul 6 14:09 Downloads
drwxr-xr-x 1 jerry jerry 0 Jul 6 14:09 Music
drwxr-xr-x 1 jerry jerry 0 Jul 6 14:09 Pictures
drwxr-xr-x 1 jerry jerry 0 Jul 6 14:09 Public
drwxr-xr-x 1 jerry jerry 0 Jul 6 14:09 Templates
drwxr-xr-x 1 jerry jerry 0 Jul 6 14:09 Videos
root@debian:~# btrfs subvol show /mnt
/mnt is btrfs root
root@debian:~# btrfs subvol list /mnt
ID 258 gen 28 top level 5 path .snapshots/home_snap
root@debian:~# btrfs subvol list /
ID 263 gen 78 top level 5 path .snapshots/root
root@debian:~# btrfs subvol list /home
ID 258 gen 28 top level 5 path .snapshots/home_snap
root@debian:~#
Ubuntu's technique puts both "@" (root) and "@home" (/home) on the same device with the same level=5. No cross linking problems and a single mount makes things easy.
The method given in the link of my previous post didn't work on a guest OS but may work on a hardware installation where run runs a rescuesystemHD to work on the unmounted HD."A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
– John F. Kennedy, February 26, 1962.Comment
-
Now, here is the beauty of the Ubuntu btrfs scheme:
Now, after an update problem I can roll back usingCode:jerry@jerry-Aspire-7739:~$ sudo su - root@jerry-Aspire-7739:~# [B]btrfs subvol list -pau / [/B] ID 257 gen 62380 parent 5 top level 5 uuid a6c08390-1f77-8148-ae75-e548a012dc06 path <FS_TREE>/@ ID 258 gen 62380 parent 5 top level 5 uuid 32f6399a-344a-aa40-8aca-c4ea86ded7b6 path <FS_TREE>/@home root@jerry-Aspire-7739:~# [B]cat /etc/fstab [/B] # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda4 during installation UUID=215f0509-7e55-475f-b438-78cf100cfc75 / btrfs defaults,subvol=@ 0 1 # /home was on /dev/sda4 during installation UUID=215f0509-7e55-475f-b438-78cf100cfc75 /home btrfs defaults,subvol=@home 0 2 root@jerry-Aspire-7739:~# [B]mount /dev/sda4 /mnt [/B] root@jerry-Aspire-7739:~#[B] vdir /mnt [/B] total 0 drwxr-xr-x 1 root root 226 Jul 6 15:46 @ drwxr-xr-x 1 root root 30 Jul 5 17:52 @home root@jerry-Aspire-7739:~# [B]btrfs subvol list -pau /mnt[/B] ID 257 gen 62385 parent 5 top level 5 uuid a6c08390-1f77-8148-ae75-e548a012dc06 path @ ID 258 gen 62384 parent 5 top level 5 uuid 32f6399a-344a-aa40-8aca-c4ea86ded7b6 path @home root@jerry-Aspire-7739:~# [B]btrfs subvol show /[/B] / Name: @ uuid: a6c08390-1f77-8148-ae75-e548a012dc06 Parent uuid: - Creation time: 2014-12-31 18:51:27 Object ID: 257 Generation (Gen): 62386 Gen at creation: 6 Parent: 5 Top Level: 5 Flags: - Snapshot(s): root@jerry-Aspire-7739:~# [B]btrfs subvol show /home[/B] /home Name: @home uuid: 32f6399a-344a-aa40-8aca-c4ea86ded7b6 Parent uuid: - Creation time: 2014-12-31 18:51:28 Object ID: 258 Generation (Gen): 62384 Gen at creation: 9 Parent: 5 Top Level: 5 Flags: - Snapshot(s): root@jerry-Aspire-7739:~# [B]btrfs subvol snapshot /mnt/@ /mnt/@_snapshot[/B] Create a snapshot of '/mnt/@' in '/mnt/@_snapshot' root@jerry-Aspire-7739:~# [B]btrfs subvol snapshot /mnt/@home /mnt/@home_snapshot[/B] Create a snapshot of '/mnt/@home' in '/mnt/@home_snapshot' root@jerry-Aspire-7739:~# [B]btrfs subvol list -pau /[/B] ID 257 gen 62388 parent 5 top level 5 uuid a6c08390-1f77-8148-ae75-e548a012dc06 path <FS_TREE>/@ ID 258 gen 62389 parent 5 top level 5 uuid 32f6399a-344a-aa40-8aca-c4ea86ded7b6 path <FS_TREE>/@home ID 469 gen 62388 parent 5 top level 5 uuid 4046a1af-bc1d-4f47-96dd-613ebf40cb23 path <FS_TREE>/@_snapshot ID 470 gen 62389 parent 5 top level 5 uuid 365c2407-a713-8549-a9a5-4ed3141e2ac2 path <FS_TREE>/@home_snapshot
and reboot.Code:sudo mv /mnt/@ /mnt/@_badroot sudo mv /mnt/@_snapshot /mnt/@
Last edited by GreyGeek; Jul 06, 2015, 03:17 PM."A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
– John F. Kennedy, February 26, 1962.Comment
-
yup easy isn't it ,,,,,,,, we did that @hear as well https://www.kubuntuforums.net/showth...l=1#post367553Originally posted by GreyGeek View Post
but what do you mean ,,, " of the Ubuntu btrfs scheme " ,,,,,,,,,is this @and @home specific to Ubuntu ?
for those of us that like to do multiple installs it would be better if the installers would let you give unique names to @ and @home so thay would install with the unique name in grub and /etc/fstab .
as is if you do a second install you first half to rename @ and @home and change the references in /etc/fstab and /boot/grub/grub.cfg to match before you do the second install which will default to @ and @home once again,,,,,, or am I confused hear.
VINNYi7 4core HT 8MB L3 2.9GHz
16GB RAM
Nvidia GTX 860M 4GB RAM 1152 cuda cores
Comment
-
The "Ubuntu" scheme is indeed @ for / and @home for /home.
I posted a how-to on this, but basically;I just do a Kubuntu install,I can then install another *buntu to the same btrfs file system and start the same process over again. My "dream" installer has the ability to specify subvolume names at install time so I wouldn't have to go through all that.
boot to it once and update it,
boot to a different install or liveUSB,
rename the subvolumes to (for example) @Kubuntu_15_04 for / and @Kubuntu_15_04_home for /home,
manually edit fstab and grub.cfg the reflect to new subvolume names,
boot into the install again,
run "update-grub",
done.
The problematic installs are like Jerry ran into where they don't use subvolumes at all. That makes it a real PITA to work with as you see above.
@GreyGeek; yes, as you discovered, snapshots cannot be done across devices, you have to use send/receive to do that.Comment
-
For fun, here's my main btrfs file system root level:
The "_ro" subvolumes are read-only snapshots I used to send the install to a backup drive.Code:stuart@office:~$ ll /mnt/samsung total 0 drwxr-xr-x 1 root root 382 May 28 12:21 @Kubuntu_14_04 drwxr-xr-x 1 root root 48 Jan 25 16:21 @Kubuntu_14_04_home drwxr-xr-x 1 root root 48 Jan 25 16:21 @Kubuntu_14_04_home_ro drwxr-xr-x 1 root root 382 Apr 8 14:16 @Kubuntu_14_04_ro drwxr-xr-x 1 root root 284 Jun 21 10:56 @Kubuntu_15_04 drwxr-xr-x 1 root root 32 Jun 1 14:40 @Kubuntu_15_04_home drwxr-xr-x 1 root root 0 May 9 08:51 snapshots drwxr-x--- 1 stuart stuart 0 Feb 21 07:14 @stuart
Comment
-
Using the "/" symbol for the <FS_ROOT> root causes the problems which the "@" symbol avoids. When I make a snapshot of "@" I can use "@_snapshot" as the name with no problems. On Jessie, when I make a snapshot of / using "/_snapshot" I get instead a snapshot named "_snapshot". To get the "/" symbol as the first character of the name I'd have to escape it, leading to annoying syntax's .Originally posted by oshunluvr View Post
I tried to mimick Ubuntu's scheme by creating a /home partition using the Btrfs as well, but that creates two devices. One cannot add the second partition to the first using Btrfs in order to create "one" partiton because it already has a root as well. To sum up, Jessie's implementation of a Btrfs file system is not well conceived, and neither is its installer."A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
– John F. Kennedy, February 26, 1962.Comment
-
Just recently, I discovered why I lost the Logout, Restart & Shutdown functionsOriginally posted by dibl View Post
of the luncher menu. This seems to happen when in dolphin I try to access any
other partitions on the hard drive. I get the message" An error occurred while
trying to access ...." Lately when this happened, I tried to reboot and noticed
the lack of response from "reboot" & "shutdown" on the luncher Menu.
Any ideas?Comment
Comment