| 1 |
Relson, David wrote: |
| 2 |
> My embedded environment is evolving. The Disk-On-Module currently |
| 3 |
> has the following partitions: |
| 4 |
> /dev/hda2 - / - root (ext2) |
| 5 |
> /dev/hda1 - /boot - syslinux boot partition (FAT16) |
| 6 |
> /dev/hda3 - /var - ext2, rw |
| 7 |
.. |
| 8 |
> How important is running fsck in an embedded ext2 environment? |
| 9 |
|
| 10 |
For read-only partitions on perfect media it is never needed. |
| 11 |
|
| 12 |
|
| 13 |
> When do y'all do and recommend? |
| 14 |
|
| 15 |
Since you are having problems related to writes, I would recommending |
| 16 |
splitting things up so that you have one physical media which is |
| 17 |
exclusively read-only, and another physical media which is |
| 18 |
read-write. This is what I use for my customers. |
| 19 |
|
| 20 |
|
| 21 |
Ed W wrote: |
| 22 |
> 1) The CF card is quietly shuffling data around, so in theory it |
| 23 |
> might move a good sector onto a patch of flash which is worn out, |
| 24 |
> causing it to be corrupted on next read. |
| 25 |
|
| 26 |
This will of course destroy a previously healthy ext2 fs. |
| 27 |
|
| 28 |
|
| 29 |
> 2) Sudden shutdowns causing the ext2 to be marked dirty and causing |
| 30 |
> subsequent problems (ie not fully read-only mounted |
| 31 |
> |
| 32 |
> To be honest, I don't know a lot about how ext2 is mounted |
| 33 |
> read-only, but option 2) above seems unlikely...? |
| 34 |
|
| 35 |
If ext2 is mounted ro then it will never be written to by the kernel |
| 36 |
and thus never corrupted by power failure. |
| 37 |
|
| 38 |
Of course, if the media itself gets corrupted for whatever reason, |
| 39 |
you lose anyway. Hence; use separate media. |
| 40 |
|
| 41 |
|
| 42 |
//Peter |
Archives