Hi Martin, Your report motivated me to fire up my test net5501 and perform the same test...
Quick test results: after 10 plug-pulled power cycles, using both Asterisk 1.8 and Asterisk 11, sometimes idle, sometimes with 1 active call and with 4 active calls when power was cut. In all cases it rebooted properly with "Fsck detected and repaired errors..." without any interaction, both for /dev/sda2 and /dev/sda3 (in my case). Here are the details of my setup: 1) net5501 using comBIOS 1.33c 2) Sandisk 1 GB CF card (older blue/red label CF, what I had installed) 3) "cat /proc/cmdline" shows libata.dma=5 which enables DMA for CF, initially set with "set-kcmd libata.dma=5" 4) At initial setup, I use "separate" partitions for ASTURW (/dev/sda2) and ASTKD '/mnt/kd/' (/dev/sda3) . I assume #1 is the same as yours, #2 is always the wildcard. If #3 is different, you probably want to change that anyway, quick and easy to do with "set-kcmd libata.dma=5" and a reboot. I assume #4 is different, if #3 does not make a difference please take the time to create a setup with separate partitions. BTW, I always setup my systems this way. Please report back with any findings. As far as supporting ext3, since the issue you describe is not common, the idea of using journaling on a flash based (limited writes) file system never seemed like a good choice for our application. Thanks for the report and hope you can resolve your issue with any of the above tweaks. Lonnie On Apr 1, 2014, at 6:05 PM, Martin Sunstrum wrote: > Hello, > > I have an Astlinux installation using the latest 1.1.4-Asterisk-11.7.0 for > our Soekris net5501 hardware. > Astlinux is installed on Sandisk compact flash card. > > In our situation, I cannot guarantee our users will not do a hard power-down > by unplugging the power cord. > Also, usage of a UPS is not an option for these installations. > > But I wasn’t too concerned, because I would expect there would be very few > configuration changes / writes to flash occurring in this system. > Once the system is setup, it might be year(s) before the configuration will > ever be changed. > > But what I have noticed is that if I perform power cord unplug tests, I see > that in about 30% of the tests, fsck will fail, requiring manual intervention > to run a fsck fixup. In the other 70% of cases, fsck will detect errors, but > will be able to fix them up, and bootup occurs properly. > > > For the 30% fsck failure rate, the console message is as follows: > > Configuring for unionfs... > Checking asturw filesystem > > ASTURW: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > (i.e., without -a or -p options) > Fsck detected errors on /dev/sda2 (4) > execute fsck -t ext2 /dev/sda2 to attempt to repair errors manually. > > > Few questions / notes > - I am using high quality Sandisk Ultra / Ultra II compact flash > disks > - During these powerdown tests, Asterisk is quite idle. Only one > device is registered, no active calls on the go. > - Is this the expected hard fsck failure rate for ext2 filesystem ? > - Is there an option to run Astlinux with a ext3 filesystem for > /dev/sda2 ? > > Thanks, Martin ------------------------------------------------------------------------------ _______________________________________________ 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].
