> You say in your original mail that after moving the data "everything was > fine". What exactly do you mean by that: > > 1. The command ended without failure so you assume it moved stuff > correctly, or > 2. You proved the move was done by mounting the partition and all your > files were there, or > 3. Some other reason? > > alan
"Everything was fine" mean; I created partition and then formatted it without any errors or warnings. There are messages from syslog: ----------------------------------------------------------------------- Jan 22 23:43:16 localhost EXT3 FS on sdb1, internal journal Jan 22 23:43:16 localhost EXT3-fs: mounted filesystem with ordered data mode. ----------------------------------------------------------------------- Then I copied my data to this new partition. I could access this data from new partition without any problems. Next day: ----------------------------------------------------------------------- Jan 23 10:23:46 localhost VFS: Can't find ext3 filesystem on dev sdb1. ----------------------------------------------------------------------- > It looks like when you moved the data onto the new partition, it got > written somewhere on the disk. However, the kernel's idea of how the > partitions are laid out at that time and what fdisk just wrote to the > disk probably don't agree and the kernel had got it wrong.... This does > happen when you delete two or more partitions and create one large one. Why it can happen when replacing two partitions with large one? I tried gpart with this output: ----------------------------------------------------------------------- #gpart /dev/sdb Begin scan... Possible partition(Windows NT/W2K FS), size(40959mb), offset(0mb) Possible partition(Linux ext2), size(197512mb), offset(40959mb) End scan. Checking partitions... Partition(OS/2 HPFS, NTFS, QNX or Advanced UNIX): primary Partition(Linux ext2 filesystem): primary Ok. Guessed primary partition table: Primary partition(1) type: 007(0x07)(OS/2 HPFS, NTFS, QNX or Advanced UNIX) size: 40959mb #s(83885696) s(63-83885758) chs: (0/1/1)-(1023/239/63)d (0/1/1)-(5547/239/62)r Primary partition(2) type: 131(0x83)(Linux ext2 filesystem) size: 197512mb #s(404505360) s(83885760-488391119) chs: (1023/239/63)-(1023/239/63)d (5548/0/1)-(32300/239/63)r Primary partition(3) type: 000(0x00)(unused) size: 0mb #s(0) s(0-0) chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r Primary partition(4) type: 000(0x00)(unused) size: 0mb #s(0) s(0-0) chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r ----------------------------------------------------------------------- I also tried it with data about cylinders, sectors and heads taken from 'fdisk -l /dev/sdb'. It produces same output. But I created ext3 on whole disk, I'm sure. -- gentoo-user@gentoo.org mailing list
