Duplicate UUID in fstab and duplicate device in mtab

[toivo]

I have duplicate UUID in fstab:
UUID=1f093d59-c7b9-4316-ab68-32f51dc1050f / ext3 defaults 1 1
UUID=492E-A498 /winsys vfat umask=0077,shortname=winnt 0 0
UUID=7eafcce0-c445-4e70-ace2-333fb5d39534 /opt ext3 defaults 1 2
UUID=42212857-292e-41aa-8875-67b3a66c6858 /usr ext3 defaults 1 2
UUID=d2ad8476-5310-478b-b70e-fd42932d37ac /usr/local ext3 defaults 1 2
UUID=44b26958-4a04-4976-9d5b-c94353093ad6 /var ext3 defaults 1 2
UUID=6a277462-c666-45d8-abf9-78a39d767944 /tmp ext3 defaults 1 2
UUID=8de11061-9f2e-44c3-8f3e-ea9987eff2c6 /home ext3 defaults 1 2
UUID=1f093d59-c7b9-4316-ab68-32f51dc1050f /data ext3 defaults 1 2
UUID=f7518a67-0bd9-4467-a094-0aa15f0ae397 /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
UUID=63513df1-348d-4a26-b895-94ad08bd6fc5 swap swap defaults 0 0

UUID for / and for /data are same.

And my mtab:

/dev/sda3 / ext3 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
/dev/sda2 /winsys vfat rw,umask=0077,shortname=winnt 0 0
/dev/sda10 /opt ext3 rw 0 0
/dev/sda8 /usr ext3 rw 0 0
/dev/sda11 /usr/local ext3 rw 0 0
/dev/sda7 /var ext3 rw 0 0
/dev/sda6 /tmp ext3 rw 0 0
/dev/sda5 /home ext3 rw 0 0
/dev/sda3 /data ext3 rw 0 0
/dev/sda1 /boot ext3 rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
gvfs-fuse-daemon /home/toivo/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=toivo 0 0

Something is wrong?
How to correct it?
I want to delete /data partition and recreate it.

Gparted shows /dev/sda3 Status: Mounted on /,/data

Gparted also shows /dev/sda9 as Filesystem: unknown
Warning : Unable to detect filesystem! Possible reasons are:
- The filesystem is damaged...

Maybe for some strange reason /data is using incorrectly /dev/sda3 instead of correct /dev/sda9

So far I have not used /data but it shows some directory's and files from root /
I assume it's because /data incorrectly overlays root /

My system is Fedora 9

[vallimar]

Use "blkid" to query current UUID's and make sure you fstab entries are up to date.
You can also use 'tune2fs -l <device>', the UUID is listed near the top.

[toivo]

[root@silent sbin]# ./blkid
/dev/sda3: LABEL="/1" UUID="1f093d59-c7b9-4316-ab68-32f51dc1050f" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda1: LABEL="/boot" UUID="f7518a67-0bd9-4467-a094-0aa15f0ae397" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda2: LABEL="/winsys" UUID="492E-A498" TYPE="vfat"
/dev/sda5: LABEL="/home" UUID="8de11061-9f2e-44c3-8f3e-ea9987eff2c6" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda6: LABEL="/tmp" UUID="6a277462-c666-45d8-abf9-78a39d767944" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda7: LABEL="/var" UUID="44b26958-4a04-4976-9d5b-c94353093ad6" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda8: LABEL="/usr" UUID="42212857-292e-41aa-8875-67b3a66c6858" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda10: LABEL="/opt" UUID="7eafcce0-c445-4e70-ace2-333fb5d39534" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda11: LABEL="/usr/local" UUID="d2ad8476-5310-478b-b70e-fd42932d37ac" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda12: TYPE="swap" LABEL="SWAP-sda12" UUID="63513df1-348d-4a26-b895-94ad08bd6fc5"
/dev/mapper/live-osimg-min: LABEL="Fedora-9-Live-i6" UUID="e1f6ab3c-812f-482e-b61b-593ac211f58f" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/live-rw: LABEL="Fedora-9-Live-i6" UUID="e1f6ab3c-812f-482e-b61b-593ac211f58f" TYPE="ext3"

No /data at all?
And neither /sda9

[root@silent sbin]# ./tune2fs -l /dev/sda3
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: /1
Last mounted on: <not available>
Filesystem UUID: 1f093d59-c7b9-4316-ab68-32f51dc1050f
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 5128192
Block count: 20480866
Reserved block count: 0
Free blocks: 20029673
Free inodes: 5117578
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 251
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Thu May 8 04:39:28 2008
Last mount time: Sat Dec 27 13:46:01 2008
Last write time: Sat Dec 27 13:46:01 2008
Mount count: 82
Maximum mount count: -1
Last checked: Thu May 8 04:48:09 2008
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Journal inode: 8
First orphan inode: 16601
Default directory hash: tea
Directory Hash Seed: 91cb71e0-e684-4c10-b873-e3e95e737bdc
Journal backup: inode blocks

[root@silent sbin]# ./tune2fs -l /dev/sda9
tune2fs 1.41.3 (12-Oct-2008)
./tune2fs: Bad magic number in super-block while trying to open /dev/sda9
Couldn't find valid filesystem superblock.


What next?

[vallimar]

According to your info, your root "/" is getting mounted twice, a second time at "/data".
You should comment out that bad entry in fstab to prevent accidents.

You can use fdisk to check if that is paritioned properly, if it is, it might be corrupted.
> fdisk /dev/sda (use 'p' to print to print table, check /dev/sda9 and see if it looks okay)

You can maybe try to fsck it if fdisk shows it to be a valid extended partition.
> e2fsck -C 0 /dev/sda9 (or man e2fsck for more options).

If none of that seems to be working, or you get massive gobs of errors,
since you've apparently never actually used it, perhaps reformat it.
> mke2fs -v -t ext3 -T largefile -L /data /dev/sda9

See the manpage for mke2fs for other settings.
After a formatting, it will should have a proper UUID, grab it and update fstab.

[toivo]

Thanks for help.
Sorry for bothering you again.

[root@silent sbin]# ./fdisk -l

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0bcc4bd9

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 650 5116702+ b W95 FAT32
/dev/sda3 651 10849 81923467+ 83 Linux
/dev/sda4 10850 38913 225424080 5 Extended
/dev/sda5 10850 13399 20482843+ 83 Linux
/dev/sda6 13400 14674 10241406 83 Linux
/dev/sda7 14675 15949 10241406 83 Linux
/dev/sda8 15950 17224 10241406 83 Linux
/dev/sda9 17225 18499 10241406 83 Linux
/dev/sda10 18500 19136 5116671 83 Linux
/dev/sda11 19137 19773 5116671 83 Linux
/dev/sda12 19774 20028 2048256 82 Linux swap / Solaris

[root@silent sbin]# ./fdisk /dev/sda

The number of cylinders for this disk is set to 38913.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): q

fdisk seems to be happy with partition table.

[root@silent sbin]# ./e2fsck -C 0 /dev/sda9
e2fsck 1.41.3 (12-Oct-2008)
./e2fsck: Superblock invalid, trying backup blocks...
./e2fsck: Bad magic number in super-block while trying to open /dev/sda9

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>


Initially (few months ago) when I created partitions during Fedora 9 install
I planned some 10 GB (or 20GB , don't remember) for root partition and
80GB for /data partition.
Now I have root partition almost 80 GB and corrupted /sda9 appr. 10GB

Is it possible to cut down root partition without losing data?

I have unused space at the end of disk, so I can create additional
partition for data and leave 80GB for root. Is this reasonable?

I plan to upgrade to Fedora 10 and maybe it's better to recreate partition's
from zero ??

I have some stability problems with Fedora 9 (installed from live CD)
- random lock ups and sometimes even kernel failures.
I tested RAM and it's OK.

Is Fedora 10 more stable?


Any recommendations?


Dec 26 16:29:57 silent kernel: ------------[ cut here ]------------
Dec 26 16:29:57 silent kernel: WARNING: at lib/list_debug.c:51 list_del+0x41/0x60()
Dec 26 16:29:57 silent kernel: list_del corruption. next->prev should be c15846d8, but was 00200200
Dec 26 16:29:57 silent kernel: Modules linked in: bridge stp bnep rfcomm l2cap bluetooth fuse sunrpc ipt_REJECT nf_conntrack_ipv4 iptable_filter ip_tables ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables x_tables cpufreq_ondemand acpi_cpufreq ipv6 vfat fat dm_mirror dm_log dm_multipath scsi_dh dm_mod snd_hda_intel sr_mod snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device i915 snd_pcm_oss snd_mixer_oss snd_pcm drm cdrom snd_timer snd_page_alloc pata_marvell snd_hwdep i2c_algo_bit snd usb_storage firewire_ohci i2c_i801 pcspkr joydev iTCO_wdt firewire_core serio_raw crc_itu_t e1000e iTCO_vendor_support i2c_core soundcore sg ata_piix pata_acpi ata_generic libata sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: microcode]
Dec 26 16:29:57 silent kernel: Pid: 2769, comm: Xorg Not tainted 2.6.27.7-53.fc9.i686 #1
Dec 26 16:29:57 silent kernel: [<c042a052>] warn_slowpath+0x4b/0x6c
Dec 26 16:29:57 silent kernel: [<c043fdf6>] ? getnstimeofday+0x3c/0xd6
Dec 26 16:29:57 silent kernel: [<c0413713>] ? lapic_next_event+0x15/0x1c
Dec 26 16:29:57 silent kernel: [<c041da7f>] ? update_curr+0x94/0xdc
Dec 26 16:29:57 silent kernel: [<c043fdf6>] ? getnstimeofday+0x3c/0xd6
Dec 26 16:29:57 silent kernel: [<c0413713>] ? lapic_next_event+0x15/0x1c
Dec 26 16:29:57 silent kernel: [<c0442833>] ? clockevents_program_event+0xe1/0xf0
Dec 26 16:29:57 silent kernel: [<c0508b99>] list_del+0x41/0x60
Dec 26 16:29:57 silent kernel: [<c0470829>] get_page_from_freelist+0x23d/0x419
Dec 26 16:29:57 silent kernel: [<c0405efe>] ? do_IRQ+0x117/0x12e
Dec 26 16:29:57 silent kernel: [<c0470c6c>] __alloc_pages_internal+0xb0/0x399
Dec 26 16:29:57 silent kernel: [<c0470f8f>] __get_free_pages+0x14/0x24
Dec 26 16:29:57 silent kernel: [<c049a30e>] __pollwait+0x4c/0xb6
Dec 26 16:29:57 silent kernel: [<c062a266>] unix_poll+0x17/0x8a
Dec 26 16:29:57 silent kernel: [<c05c9af3>] sock_poll+0xf/0x12
Dec 26 16:29:57 silent kernel: [<c0499ba3>] do_select+0x2c4/0x4bb
Dec 26 16:29:57 silent kernel: [<c049a2c2>] ? __pollwait+0x0/0xb6
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0423e0f>] ? default_wake_function+0x0/0xd
Dec 26 16:29:57 silent kernel: [<c0499eba>] core_sys_select+0x120/0x1a3
Dec 26 16:29:57 silent kernel: [<c043d61d>] ? __remove_hrtimer+0x5f/0x67
Dec 26 16:29:57 silent kernel: [<c0643e63>] ? _spin_unlock_irqrestore+0x22/0x38
Dec 26 16:29:57 silent kernel: [<c043decc>] ? hrtimer_try_to_cancel+0x61/0x6b
Dec 26 16:29:57 silent kernel: [<c042d809>] ? do_setitimer+0x171/0x336
Dec 26 16:29:57 silent kernel: [<c049a202>] sys_select+0x88/0x148
Dec 26 16:29:57 silent kernel: [<c040a100>] ? syscall_trace_enter+0xb5/0xc9
Dec 26 16:29:57 silent kernel: [<c0403cca>] syscall_call+0x7/0xb
Dec 26 16:29:57 silent kernel: =======================
Dec 26 16:29:57 silent kernel: ---[ end trace c63298f4fb1b33f0 ]---

[vallimar]

If parted / gparted will let you do it, go for it. Keep in mind that it isn't a simple operation
because they aren't logical volumes and they also aren't next to eachother on the disk.
Fedora 10 being better / more stable is entirely subjective to each person. It's better, the same
or worse depending on who you ask.