Re: 9.0 crash, ssd or filesystem problem?
On 11/16/12 21:38, Warren Block wrote: On Fri, 16 Nov 2012, Gary Aitken wrote: On 11/16/12 12:10, Warren Block wrote: Additional SSD suggestions: when creating partitions, leave out the swap partition. If you have lots of memory, leave out the /tmp partition. Add that extra space to the /usr partition. Format the UFS filesystems with -Ut, for soft updates and TRIM support. (Make sure your SSD supports TRIM, almost all do.) (I don't use soft updates journaling.) Use dd(1) to make a zero-filled file on /usr somewhere, say /usr/swap. Make it the size you want swap to be, and do not make it a sparse file. Tell the system to use the swapfile in /etc/rc.conf: swapfile=/usr/swap Use tmpfs for /tmp in /etc/fstab: tmpfs/tmptmpfsrw,mode=0177700 When using the above in /etc/fstab to establish a tmp file, how does the size of /tmp get established? Is it limited only by the available swap, or is it possible to put an upper bound on it that is smaller than swap? e.g. if I built it manually: mdconfig -a -t swap -s 1g -u 1 newfs -U /dev/md1 mount /dev/md1 /tmp chmod 1777 /tmp wouldn't it be limited to 1g of swap space? Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
On 11/15/12 15:56, Warren Block wrote: On Thu, 15 Nov 2012, Gary Aitken wrote: Trying to rebuild ports, I'm consistently getting the following: ahcich1 Timeout on slot 13 port 0 ^ slot varies g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 That seems familiar, maybe others have reported it. Is this a motherboard controller, or add-in? mobo. Asus M4A89TD PRO/USB3 specs say AMD SB850 controller After a backup, I'd make sure the motherboard and controller BIOS are up to date. And also the SSD firmware. Thanks for the reminder, I see there is a new one. ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
On Fri, 16 Nov 2012, Gary Aitken wrote: ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. That's a normal install. It's fine for 512-byte devices. I have other suggestions too, but let's save that until the problem is fixed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. That's a normal install. It's fine for 512-byte devices. I have other suggestions too, but let's save that until the problem is fixed. aaahhh. Vague recollections of getting this to boot up first time around. How about suggestions anyway, as I'm going to build an sata disk and move things to that as part of the process to see what's wrong. May as well get it right-ish the first time; then repartition the SSD. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
On Fri, 16 Nov 2012, Gary Aitken wrote: ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. That's a normal install. It's fine for 512-byte devices. I have other suggestions too, but let's save that until the problem is fixed. aaahhh. Vague recollections of getting this to boot up first time around. How about suggestions anyway, as I'm going to build an sata disk and move things to that as part of the process to see what's wrong. May as well get it right-ish the first time; then repartition the SSD. Okay. The disk setup article shows alignment and using GPT labels, so I'll skip those. Additional SSD suggestions: when creating partitions, leave out the swap partition. If you have lots of memory, leave out the /tmp partition. Add that extra space to the /usr partition. Format the UFS filesystems with -Ut, for soft updates and TRIM support. (Make sure your SSD supports TRIM, almost all do.) (I don't use soft updates journaling.) Use dd(1) to make a zero-filled file on /usr somewhere, say /usr/swap. Make it the size you want swap to be, and do not make it a sparse file. Tell the system to use the swapfile in /etc/rc.conf: swapfile=/usr/swap Use tmpfs for /tmp in /etc/fstab: tmpfs /tmptmpfs rw,mode=01777 0 0 It's possible to limit the size, but not necessary. This /tmp will be cleared on reboot. Now: why? Using a swapfile through the filesystem gives three advantages: 1. Disk space is not tied up in an unused swap partition. 2. Swap can be resized without repartitioning. 3. Swap goes through the filesystem, using TRIM, helping the SSD maintain performance. /tmp as tmpfs is auto-sizing, efficient, and self-clearing on reboot. It doesn't tie up disk space in a mostly-unused partition. I use tmpfs for /usr/obj also. It doesn't improve speed, but reduces writes to SSD and is also self-clearing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
On 11/16/12 12:10, Warren Block wrote: ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. That's a normal install. It's fine for 512-byte devices. I have other suggestions too, but let's save that until the problem is fixed. aaahhh. Vague recollections of getting this to boot up first time around. After upgrading the mobo bios I re-partitioned and so far so good although ports are messed up and I'll have to rebuild them. Did not implement the suggestions below as I needed to get back up and figured it would take me a while to get it right. Will do that on the new disk. How about suggestions anyway, as I'm going to build an sata disk and move things to that as part of the process to see what's wrong. May as well get it right-ish the first time; then repartition the SSD. Okay. The disk setup article shows alignment and using GPT labels, so I'll skip those. Additional SSD suggestions: when creating partitions, leave out the swap partition. If you have lots of memory, leave out the /tmp partition. Add that extra space to the /usr partition. Format the UFS filesystems with -Ut, for soft updates and TRIM support. (Make sure your SSD supports TRIM, almost all do.) (I don't use soft updates journaling.) Use dd(1) to make a zero-filled file on /usr somewhere, say /usr/swap. Make it the size you want swap to be, and do not make it a sparse file. Tell the system to use the swapfile in /etc/rc.conf: swapfile=/usr/swap Use tmpfs for /tmp in /etc/fstab: tmpfs/tmptmpfsrw,mode=0177700 It's possible to limit the size, but not necessary. This /tmp will be cleared on reboot. Not necessary because it is constrained by the swap file size? Now: why? Using a swapfile through the filesystem gives three advantages: 1. Disk space is not tied up in an unused swap partition. 2. Swap can be resized without repartitioning. 3. Swap goes through the filesystem, using TRIM, helping the SSD maintain performance. /tmp as tmpfs is auto-sizing, efficient, and self-clearing on reboot. It doesn't tie up disk space in a mostly-unused partition. I use tmpfs for /usr/obj also. It doesn't improve speed, but reduces writes to SSD and is also self-clearing. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
On Fri, 16 Nov 2012, Gary Aitken wrote: On 11/16/12 12:10, Warren Block wrote: Additional SSD suggestions: when creating partitions, leave out the swap partition. If you have lots of memory, leave out the /tmp partition. Add that extra space to the /usr partition. Format the UFS filesystems with -Ut, for soft updates and TRIM support. (Make sure your SSD supports TRIM, almost all do.) (I don't use soft updates journaling.) Use dd(1) to make a zero-filled file on /usr somewhere, say /usr/swap. Make it the size you want swap to be, and do not make it a sparse file. Tell the system to use the swapfile in /etc/rc.conf: swapfile=/usr/swap Use tmpfs for /tmp in /etc/fstab: tmpfs/tmptmpfsrw,mode=0177700 It's possible to limit the size, but not necessary. This /tmp will be cleared on reboot. Not necessary because it is constrained by the swap file size? Yes, but also because /tmp usually doesn't need much space. On this desktop system, du shows all of /tmp is only 52K. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
9.0 crash, ssd or filesystem problem?
Trying to rebuild ports, I'm consistently getting the following: ahcich1 Timeout on slot 13 port 0 ^ slot varies g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 /usr got error 6 while accessing filesyustem cpuid=0 panic: softdep_deallocate_dependencies:unrecovered I/O error KBD: stack backtrace: #0 ... kbd_backtrace+0x5e #1 ... panic+0x187 #2 ... clear_remove+0 #3 ... brelse+0x60 (ada0:ahcich1:0:0:0): lost device #4 ... bufdone+0x68 #5 ... g_io_schedule_up+0xa6 #6 ... fork_exit+0x11f #7 ... fork_trampoline+0xe This happens consistently when doing portmaster www/firefox ... firefox-16.0.2,1 depends on file: /usr/local/bin/perl5.12.4 - found The firefox build said it was going to build audio/alsa also, so to make things easier after rebooting I would do portmaster audio/alsa which would succeed, and then again try portmaster www/firefox which would always fail the same way. The interesting part about the above is that after the crash, the firefox build would say it needed to build audio/alsa again. I tried doing portmaster lang/perl5.12 to rebuild perl and get it placed somewhere different on the ssd, but I'm still getting a consistent crash after I get the firefox-16.0.2,1 depends on file: /usr/local/bin/perl5.12.4 - found line. I'm guessing it's crashing on something after the perl; how to find out what it is? Error 6 is ENXIO, device not configured; not sure exactly what that means. This machine has: 16G mem 0.5G swap 2G /tmp 4G /var Is any of that likely to be related to the problem? Given an addr in the failure error: g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 how does one relate that addr to the partitioning scheme? ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) Thanks for any insights, Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
On Thu, Nov 15, 2012 at 1:18 PM, Gary Aitken free...@dreamchaser.orgwrote: Error 6 is ENXIO, device not configured; not sure exactly what that means. This machine has: 16G mem 0.5G swap 2G /tmp 4G /var Is any of that likely to be related to the problem? Given an addr in the failure error: g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 how does one relate that addr to the partitioning scheme? ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) Thanks for any insights, Sounds like you have bad hardware. Drive, cable, controller etc. Probably wouldn't hurt to do a fsck either. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
On Thu, 15 Nov 2012 13:30:43 -0600 Adam Vande More amvandem...@gmail.com wrote: Sounds like you have bad hardware. Drive, cable, controller etc. Probably wouldn't hurt to do a fsck either. *After* identifying and fixing the hardware problem, otherwise you may make things worse. -- Steve O'Hara-Smith at...@sohara.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 crash, ssd or filesystem problem?
On Thu, 15 Nov 2012, Gary Aitken wrote: Trying to rebuild ports, I'm consistently getting the following: ahcich1 Timeout on slot 13 port 0 ^ slot varies g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 That seems familiar, maybe others have reported it. Is this a motherboard controller, or add-in? After a backup, I'd make sure the motherboard and controller BIOS are up to date. And also the SSD firmware. ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 on SSD
On Sat, 2 Jun 2012, Victor Sudakov wrote: Warren Block wrote: Thank you very much for the useful tips. One more question regarding SSD. The FreeBSD installer enabled journaled soft-updates on the filesystem which resides on the SSD. Is it good, bad or irrelevant for the SSD ? Mostly irrelevant, I think. I've been using just ordinary soft updates as there is bug fixing going on with SU+J. fsck on the SSD is very fast anyway, so SU+J is needed less. And there's a little less writing because there is no journal. But then, I've left atime on, too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 on SSD
filesystem which resides on the SSD. Is it good, bad or irrelevant for the SSD ? Mostly irrelevant, I think. I've been using just ordinary soft updates as there is bug fixing going on with SU+J. fsck on the SSD is very fast anyway, so SU+J is needed less. And there's a little less writing because there is no journal. But then, I've left atime on, too. ___ i have FreeBSD 9 and SSD (OCZ Agility 3 60GB) DO NOT use any kind of journalling - this increase writes and wear, while fsck takes 10 seconds for me. do use -t option for newfs. make sure your FS partition is aligned to 4 kilobytes. All these web advices about aligning to 1MB is classic pure nonsense (most often used NTFS aligns to 4kB anyway). run without swap or make pseudo-dynamic swap with mdconfig ;) My config: 1) no MSDOS partitions (slices). not needed no matter if it is SSD or not. unless you run windoze too. 2) single partition for FreeBSD, SSD are not huge and wasting space for partitions isn't smart. example: # /dev/ada0: 8 partitions: # size offsetfstype [fsize bsize bps/cpg] a: 117231408 04.2BSD0 0 0 c: 117231408 0unused0 0 # raw part, don't edit 3) newfs -m 0 -i 16384 -b 8192 -f 1024 -U -t /dev/ada0a or similar settings. maybe you can run with less inodes (in my case i've got 3.6M inodes). for rare case swapping i do in /etc/rc.local #!/bin/sh echo creating swapfile /bin/rm -f /swapfile.tmp dd if=/dev/zero of=/swapfile.tmp bs=8m seek=1k count=0 /sbin/mdconfig -a -t vnode -u 0 -f /swapfile.tmp || /bin/sh /bin/rm -f /swapfile.tmp /sbin/swapctl -a /dev/md0 and in /etc/rc.shutdown.local #!/bin/sh echo removing swapfile /sbin/swapctl -d /dev/md0 /sbin/mdconfig -d -u 0 this will allocate 8GB file with holes, space would be allocated when actually needed, and deallocated on shutdown. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 on SSD
Warren Block wrote: [dd] I have not done any tricky partition alignment, do I really need to? Is anything else advisable? If it's not aligned, there can be a pretty significant performance drop. Please show the output of 'gpart show' on that drive if it's GPT (gpart show ada0) or drive and slice if it's MBR/bsdlabel (gpart show ada0 gpart show ada0s1). It was created by the Auto option of the new FreeBSD installer: [sudakov@vas ~] gpart show ada0 = 34 117231341 ada0 GPT (55G) 34128 1 freebsd-boot (64k) 162 48928 2 freebsd-ufs (53G) 490905861376 3 freebsd-swap (2.8G) 117010466 220909- free - (107M) That is not aligned, either with 4K or 1M: (162*512)/4096 = 20.25 If the performance is good enough, leave it alone. Use # diskinfo -tv /dev/ada0p2 to get an optimistic version, or do some in-depth benchmarking with benchmarks/bonnie++. To get it aligned, back up and repartition: [dd] Warren, Thank you very much for the useful tips. One more question regarding SSD. The FreeBSD installer enabled journaled soft-updates on the filesystem which resides on the SSD. Is it good, bad or irrelevant for the SSD ? /dev/ada0p2 on / (ufs, local, noatime, journaled soft-updates, nfsv4acls) -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 on SSD
On Thu, 31 May 2012, Victor Sudakov wrote: Colleagues, I have installed 9.0-RELEASE on a SSD drive with the following tweaking so far: 1. tmpmfs=YES (WRKDIRPREFIX etc will go there too). 2. mount -o noatime 3. tunefs -t enable I have not done any tricky partition alignment, do I really need to? Is anything else advisable? If it's not aligned, there can be a pretty significant performance drop. Please show the output of 'gpart show' on that drive if it's GPT (gpart show ada0) or drive and slice if it's MBR/bsdlabel (gpart show ada0 gpart show ada0s1). There is one thing that worries me, why is TRIM not shown as enabled in camcontrol output? [root@vas ~] tunefs -p /dev/ada0p2 | grep -i trim tunefs: trim: (-t) enabled [root@vas ~] camcontrol identify ada0 | egrep '^Fea|TRIM' Feature Support Enabled Value Vendor data set management (TRIM) yes [root@vas ~] I think that no value there means it cannot be enabled or disabled; it's always on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 on SSD
Warren Block wrote: I have installed 9.0-RELEASE on a SSD drive with the following tweaking so far: 1. tmpmfs=YES (WRKDIRPREFIX etc will go there too). 2. mount -o noatime 3. tunefs -t enable I have not done any tricky partition alignment, do I really need to? Is anything else advisable? If it's not aligned, there can be a pretty significant performance drop. Please show the output of 'gpart show' on that drive if it's GPT (gpart show ada0) or drive and slice if it's MBR/bsdlabel (gpart show ada0 gpart show ada0s1). It was created by the Auto option of the new FreeBSD installer: [sudakov@vas ~] gpart show ada0 = 34 117231341 ada0 GPT (55G) 34128 1 freebsd-boot (64k) 162 48928 2 freebsd-ufs (53G) 490905861376 3 freebsd-swap (2.8G) 117010466 220909- free - (107M) [sudakov@vas ~] There is one thing that worries me, why is TRIM not shown as enabled in camcontrol output? [root@vas ~] tunefs -p /dev/ada0p2 | grep -i trim tunefs: trim: (-t) enabled [root@vas ~] camcontrol identify ada0 | egrep '^Fea|TRIM' Feature Support Enabled Value Vendor data set management (TRIM) yes [root@vas ~] I think that no value there means it cannot be enabled or disabled; it's always on. Oh. Thanks. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 on SSD
On Fri, 1 Jun 2012, Victor Sudakov wrote: Warren Block wrote: I have installed 9.0-RELEASE on a SSD drive with the following tweaking so far: 1. tmpmfs=YES (WRKDIRPREFIX etc will go there too). 2. mount -o noatime 3. tunefs -t enable I have not done any tricky partition alignment, do I really need to? Is anything else advisable? If it's not aligned, there can be a pretty significant performance drop. Please show the output of 'gpart show' on that drive if it's GPT (gpart show ada0) or drive and slice if it's MBR/bsdlabel (gpart show ada0 gpart show ada0s1). It was created by the Auto option of the new FreeBSD installer: [sudakov@vas ~] gpart show ada0 = 34 117231341 ada0 GPT (55G) 34128 1 freebsd-boot (64k) 162 48928 2 freebsd-ufs (53G) 490905861376 3 freebsd-swap (2.8G) 117010466 220909- free - (107M) That is not aligned, either with 4K or 1M: (162*512)/4096 = 20.25 If the performance is good enough, leave it alone. Use # diskinfo -tv /dev/ada0p2 to get an optimistic version, or do some in-depth benchmarking with benchmarks/bonnie++. To get it aligned, back up and repartition: (Back up first!) # gpart destroy -F ada0 # gpart create -s gpt ada0 # gpart add -t freebsd-boot -s 512k ada0 # gpart bootcode -b /boot/pmbr -p /boot/gptboot -i1 ada0 # gpart add -t freebsd-ufs -b 1m -s 53G ada0 # gpart add -t freebsd-swap ada0 That creates a 512k boot partition which allows for growth of the boot code. Then the UFS partition starts at 1M, an even multiple of both 4k and 1M for alignment, and a common semi-standard. Then swap fills out the drive; that could be reduced by giving a -s size if you want to leave that 107M at the end for something else. (gpart's -a option is not used. It isn't needed here, and overrides the -b option in earlier versions of gpart.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
9.0 on SSD
Colleagues, I have installed 9.0-RELEASE on a SSD drive with the following tweaking so far: 1. tmpmfs=YES (WRKDIRPREFIX etc will go there too). 2. mount -o noatime 3. tunefs -t enable I have not done any tricky partition alignment, do I really need to? Is anything else advisable? There is one thing that worries me, why is TRIM not shown as enabled in camcontrol output? [root@vas ~] tunefs -p /dev/ada0p2 | grep -i trim tunefs: trim: (-t) enabled [root@vas ~] camcontrol identify ada0 | egrep '^Fea|TRIM' Feature Support Enabled Value Vendor data set management (TRIM) yes [root@vas ~] -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org