I have now added a /var, and /data (for the jails) and a swap onto the standard drive.
Now I have # mount /dev/ad0s1a on / (ufs, local, noatime) devfs on /dev (devfs, local, multilabel) /dev/ad1s1d on /var (ufs, local, soft-updates) /dev/ad1s1e on /data (ufs, local, soft-updates) # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ad1s1b none swap sw 0 0 /dev/ad0s1a / ufs rw,noatime 1 1 /dev/ad1s1d /var ufs rw 0 2 /dev/ad1s1e /data ufs rw 0 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 ad0 is 4G CF ad1 is a laptop drive I didn't ask for "soft-updates"; it seems to be the default. Is it good/bad/doesn't matter on something like a net5501 ? Reliability and crash recovery are more important to me than performance. Are my dump and pass settings right? I haven't put any actual data on it yet so I could still change it. thanks, Philip On 04/06/12 13:18, Jim Pingle wrote: > On 6/3/2012 3:27 PM, Philip wrote: >> 1. I get these complaints in dmesg >> ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> >> LBA=7813119 >> ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> >> LBA=7813119 >> but other than that it seems fine > > That's normal for certain CF cards, especially certain Sandisk cards. > Full explanation here: > http://doc.pfsense.org/index.php/DMA_and_LBA_Errors#CF_NID_Not_Found_Error > (Basically: it's annoying but harmless) > >> 2. Thinking about flash drive wearout, I set option "rw,noatime" in fstab as >> my understanding is >> that this is a good idea with solid state drives. Presumably I should >> disable swap on the CF and >> put a swap partition on the laptop drive? Should I mount /var on the laptop >> drive as well? what >> about other partitions? the jails will be on there. I would like to be >> able to survive a hard >> drive failure without the whole thing failing (there will be scripts to back >> up the jails elsewhere). > > You definitely do not want swap on the CF. As for /var, that's > debatable. You might consider running NanoBSD instead of straight > FreeBSD as it's geared more toward CF, but I'm not sure if there are any > pre-built NanoBSD images for FreeBSD floating around. > > For pfSense (based on FreeBSD) on CF, we use NanoBSD style build, and > /tmp and /var are both run from a memory disk. > >> 3. Last question, but a long one :-) are there any problems with my kernel >> config below. Maybe it >> will be useful to someone else. I figured that it might be useful to be >> able to attach a usb drive >> or cdrom but I'm not interested in much else. > > Didn't look at it in depth, but you should probably be using the > templated style rather than copying GENERIC these days (e.g. you just > "include GENERIC" and then specify only the things to add/remove from > your custom file. That is easier to maintain in the long run since you > don't have to worry about updating it much every time FreeBSD changes > what is included in GENERIC. > > Jim _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
