pata drive size being confused with sata drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Ubuntu Hardy 2.6.24-19-server
I have a system with mixed pata and sata drives, the boot drive is the first sata drive (sdb1). sda1 is a 160G partition on a pata drive, sdb1 is a 10G partition on an sata drive. Parted and cfdisk both report the sizes correctly, however, If I try to put 15G of files on the /dev/sda1, it gives an out of space error. It appears that the system is using the size of sdb1 instead of sda1. Prior to installing Hardy, this system was using Debian Sid, and the drive sizes were correct.
output of: df -H
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 10G 4.4G 5.1G 47% /
varrun 1.1G 234k 1.1G 1% /var/run
varlock 1.1G 0 1.1G 0% /var/lock
udev 1.1G 58k 1.1G 1% /dev
devshm 1.1G 0 1.1G 0% /dev/shm
/dev/sdb6 490G 369G 121G 76% /media/
/dev/sdd1 501G 473G 28G 95% /media/
/dev/sdc1 751G 177G 574G 24% /media/local/tv
/dev/sda1 10G 157M 9.3G 2% /media/local/new
-------
output of: parted /dev/sda1 print
Disk /dev/sda1: 164GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00kB 164GB 164GB ext3
-------
output of: parted /dev/sdb1 print
Disk /dev/sdb1: 10.0GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00kB 10.0GB 10.0GB ext3
-------
fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdb1
UUID=d788c819-
# /dev/sdb5
UUID=2da8de0f-
#/dev/sdb6
UUID="b3ada132-
#/dev/sdc1
UUID="0b5a1713-
#/dev/sdd1
UUID="a5cabf7f-
#/dev/sda1
UUID="d8a9f30b-
[This is an automated message. Apologies if it has reached you inappropriately.]
This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue. Thanks.