HD mounting issue: df and fstab

Llama · 2015-09-26 08:41:27

Hi,

I've got some confusing df output:

$ df -h
Filesystem Size Used Avail Use% Mounted on
dev 5.9G 0 5.9G 0% /dev
run 5.9G 928K 5.9G 1% /run
/dev/sda2 31G 24G 6.1G 80% /
tmpfs 5.9G 232K 5.9G 1% /dev/shm
tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup
tmpfs 5.9G 150M 5.8G 3% /tmp
/dev/sdb4 2.7T 1.2T 1.4T 46% /home
tmpfs 1.2G 16K 1.2G 1% /run/user/1000

My home is actually on sda3. sdb is actually a target drive for cloning not yet completed. fstab looks just right, IMHO:

$ cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2 LABEL=RootS
UUID=699027fe-9b9f-42f5-9194-803c5d845184 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda3 LABEL=HomeS
UUID=36d38ac9-c79a-4a7d-a44f-45887ab0a74a /home ext4 rw,relatime,data=ordered 0 2
/dev/sda1 none swap defaults 0 0
/home/alexey /export/alexey none bind 0 0

Meanwhile, I'm really interested in checking my real /home (sda3) free space . What's wrong?
It really looks like sdb4 is mounted as /home instead of sda3 in contravention of the fstab contents. I've noticed it quite by chance, since sda3 content is already copied to sdb4.

WorMzy · 2015-09-26 08:52:06

How did you copy it?

Please post the output of

# blkid

Also, please use code tags, rather than quote tags, when pasting config files and output.

mich41 · 2015-09-26 09:15:34

If you copied the whole filesystem using dd or some low level cloning utitity then both sda3 and sdb4 ended up with the same UUID and which of them ends up mounted on /home is pretty much left to chance. You may want to temporarily replace UUID=blah with /dev/sda3 until you complete HDD migration and get rid of the old HDD. Alternatively, there may be some simple way to change the UUID of sdb4; in the worst case a hex editor would do the job

Llama · 2015-09-26 11:52:18

$ sudo blkid
[sudo] password for alexey: 
/dev/sda1: UUID="7067b5d4-a7fc-48de-b7af-caab80909fc8" TYPE="swap" PARTUUID="000ef9d3-01"
/dev/sda2: LABEL="RootS" UUID="699027fe-9b9f-42f5-9194-803c5d845184" TYPE="ext4" PARTUUID="000ef9d3-02"
/dev/sda3: LABEL="HomeS" UUID="36d38ac9-c79a-4a7d-a44f-45887ab0a74a" TYPE="ext4" PARTUUID="000ef9d3-03"
/dev/sdb2: UUID="6bfb0b5b-bead-4aed-9865-bb780d0d90f1" TYPE="swap" PARTUUID="cac8c246-aebe-459b-80f0-5da5933a7870"
/dev/sdb3: LABEL="RootS" UUID="699027fe-9b9f-42f5-9194-803c5d845184" TYPE="ext4" PARTUUID="0f63e259-a3ec-400d-b035-8d2e01271faa"
/dev/sdb4: LABEL="HomeS" UUID="36d38ac9-c79a-4a7d-a44f-45887ab0a74a" TYPE="ext4" PARTUUID="b5ff25cf-1555-41c8-aa36-2327fc349076"
/dev/sdb1: PARTUUID="20fbe5e4-4cde-4da3-af76-409f4dcde113"
/dev/sdc: UUID="F074-DB1A" TYPE="vfat"
/dev/sdd1: UUID="F4A8-9DE4" TYPE="vfat"

For cloning I used clonezilla CD. I haven't yet managed to finalize cloning; no grub2 installed yet. I haven't got much spare time and can't proceed without thinking being forced to move from MBR to GPT. Apparently my /home lives on sdb4 for a month already, without me being aware of it .

What did I do? Regenerated fstab accidentally?

WorMzy · 2015-09-26 14:52:29

As mich41 said, your "new" partitions on sdb have the same UUIDs as their counterparts on sda. You will either need to switch to device node notation in fstab (not recommended, since these are not static), or change the UUID of the new partitions using tune2fs and uuidgen.

Arch Linux

#1 2015-09-26 08:41:27

HD mounting issue: df and fstab

#2 2015-09-26 08:52:06

Re: HD mounting issue: df and fstab

#3 2015-09-26 09:15:34

Re: HD mounting issue: df and fstab

#4 2015-09-26 11:52:18

Re: HD mounting issue: df and fstab

#5 2015-09-26 14:52:29

Re: HD mounting issue: df and fstab

Board footer