Hi Martin,

>       Small side note: This image has console with 19200 baud 
>               ... different from other images (eg. Alix image starts at
> 38400) ... not a biggie

All the AstLinux serial console images default to 19200 baud, with the 
exception for the Alix which is 38400.


>       But I will proceed to re-test using the dual partitions, and let you
> know how that goes.
> 
>       What is your reasoning behind using dual partitions ?

With a single partition, unionfs is used for all the flash disk IO, including 
the /mnt/kd/ mount where most all the RW activity is.

With a dual partition, unionfs is mostly for reads where the ASTURW partition 
is seldom written to, and then the /mnt/kd/ mount is a standard ext2 partition 
without unionfs.

My theory (and not everyone agrees with me :-) ) is the KISS principle, use the 
unionfs overlay where needed (make /etc/ editable, add Asterisk sound files, 
etc.) and not use unionfs for the file system where most of the RW activity is 
at, the /mnt/kd/ mount.

It would seem to reason that with less code, less buffers, where most all the 
RW activity is, would be more immune to abrupt power failures.


> ---------------------------
> Still curious about ext3 ...

> My thinking on this comes from articles such as
> http://www.embeddedarm.com/about/resource.php?item=459

Interesting, but clearly ext3 will shorten the life of flash compared to ext2, 
but how much with modern flash wear leveling I'm not sure.

I'm sure the AstLinux team is open to re-consider ext3, but any benefit must 
outweigh the negatives.

I personally have all my AstLinux boxes on some sort of UPS, some only a small, 
inexpensive 600VA UPS... mostly to keep data flowing and calls active if there 
was a short power interruption.

Lonnie




On Apr 1, 2014, at 10:21 PM, Martin Sunstrum wrote:

> Thanks Lonnie for the quick feedback ...
> 
> Regarding you points in your message ....
> 
> 1) net5501 using comBIOS 1.33c
> 
>       I had version 1.33 ... just did an update to 1.33c
> 
>       Before proceeding to the other items, I did my tests again, and I
> could re-create the bad fsck failure ...
>       Hence, not likely the BIOS as a source of the problem.
> 
> 2) Sandisk 1 GB CF card (older blue/red label CF, what I had installed)
> 
>       I have various 2GB and 8GB cards
> 
> 3) "cat /proc/cmdline" shows libata.dma=5 which enables DMA for CF,
> initially set with "set-kcmd libata.dma=5"
> 
>       My cmdline is as follows:
> 
>       root=/dev/ram0 rw init=/linuxrc astimg=astlinux-1.1.4.run
> astlinux=net5501 astkd=auto asturw=auto astlive libata.dma=3
> console=ttyS0,19200n8
> 
>       I have changed libata.dma=5 ... but still was able to get the bad
> fsck issue. Strange ...
> 
> 
>       Small side note: This image has console with 19200 baud 
>               ... different from other images (eg. Alix image starts at
> 38400) ... not a biggie
> 
> 
> 4) At initial setup, I use "separate" partitions for ASTURW (/dev/sda2) and
> ASTKD '/mnt/kd/' (/dev/sda3) .
> 
>       I was thinking of this also. But I had previously tried this on a
> board (before applying 1) and 3) ) but still saw the bad fsck issue. (it
> would fail on /sda2 ... not /sda3)
> 
>       But I will proceed to re-test using the dual partitions, and let you
> know how that goes.
> 
>       What is your reasoning behind using dual partitions ?
> 
> ---------------------------
> Still curious about ext3 ...
> Seems to be some previous code support in Astlinux for it.
> 
> My thinking on this comes from articles such as
> http://www.embeddedarm.com/about/resource.php?item=459
> 
>     Linux offers many filesystems, but we have been able to expose bugs in
> most of them in at least some kernel versions.
>     The only one we have complete confidence in is ext3. 
>     When in doubt, ext3 should be used for any partition that will be
> mounted read-write.
> 
>     The ext2 filesystem is much more fragile. 
>     It is a perfectly good filesystem for systems that are able to mount it
> read-only, or unmount it correctly. 
>     But our experience shows that corruption is extremely likely with a
> power failure on ext2.


------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].

Reply via email to