1 |
> You say in your original mail that after moving the data "everything was |
2 |
> fine". What exactly do you mean by that: |
3 |
> |
4 |
> 1. The command ended without failure so you assume it moved stuff |
5 |
> correctly, or |
6 |
> 2. You proved the move was done by mounting the partition and all your |
7 |
> files were there, or |
8 |
> 3. Some other reason? |
9 |
> |
10 |
> alan |
11 |
|
12 |
"Everything was fine" mean; I created partition and then formatted it |
13 |
without any errors or warnings. There are messages from syslog: |
14 |
----------------------------------------------------------------------- |
15 |
Jan 22 23:43:16 localhost EXT3 FS on sdb1, internal journal |
16 |
Jan 22 23:43:16 localhost EXT3-fs: mounted filesystem with ordered data |
17 |
mode. |
18 |
----------------------------------------------------------------------- |
19 |
Then I copied my data to this new partition. I could access this data |
20 |
from new partition without any problems. Next day: |
21 |
----------------------------------------------------------------------- |
22 |
Jan 23 10:23:46 localhost VFS: Can't find ext3 filesystem on dev sdb1. |
23 |
----------------------------------------------------------------------- |
24 |
|
25 |
> It looks like when you moved the data onto the new partition, it got |
26 |
> written somewhere on the disk. However, the kernel's idea of how the |
27 |
> partitions are laid out at that time and what fdisk just wrote to the |
28 |
> disk probably don't agree and the kernel had got it wrong.... This does |
29 |
> happen when you delete two or more partitions and create one large one. |
30 |
|
31 |
Why it can happen when replacing two partitions with large one? |
32 |
|
33 |
I tried gpart with this output: |
34 |
----------------------------------------------------------------------- |
35 |
#gpart /dev/sdb |
36 |
Begin scan... |
37 |
Possible partition(Windows NT/W2K FS), size(40959mb), offset(0mb) |
38 |
Possible partition(Linux ext2), size(197512mb), offset(40959mb) |
39 |
End scan. |
40 |
|
41 |
Checking partitions... |
42 |
Partition(OS/2 HPFS, NTFS, QNX or Advanced UNIX): primary |
43 |
Partition(Linux ext2 filesystem): primary |
44 |
Ok. |
45 |
|
46 |
Guessed primary partition table: |
47 |
Primary partition(1) |
48 |
type: 007(0x07)(OS/2 HPFS, NTFS, QNX or Advanced UNIX) |
49 |
size: 40959mb #s(83885696) s(63-83885758) |
50 |
chs: (0/1/1)-(1023/239/63)d (0/1/1)-(5547/239/62)r |
51 |
|
52 |
Primary partition(2) |
53 |
type: 131(0x83)(Linux ext2 filesystem) |
54 |
size: 197512mb #s(404505360) s(83885760-488391119) |
55 |
chs: (1023/239/63)-(1023/239/63)d (5548/0/1)-(32300/239/63)r |
56 |
|
57 |
Primary partition(3) |
58 |
type: 000(0x00)(unused) |
59 |
size: 0mb #s(0) s(0-0) |
60 |
chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r |
61 |
|
62 |
Primary partition(4) |
63 |
type: 000(0x00)(unused) |
64 |
size: 0mb #s(0) s(0-0) |
65 |
chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r |
66 |
----------------------------------------------------------------------- |
67 |
I also tried it with data about cylinders, sectors and heads taken from 'fdisk -l /dev/sdb'. |
68 |
It produces same output. But I created ext3 on whole disk, I'm sure. |
69 |
|
70 |
|
71 |
-- |
72 |
gentoo-user@g.o mailing list |