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
Filesystem problem
Hi, I know this may not be the correct place to post this, but I feel like I'm going to get more help here than in the ejabberd forums. Maybe you can help me to debug what is going on here: I'm runing ejabberd-2.1-2 on FreeBSD it05 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Suddenly, my /var partition is running out of space. When I run df -h, i get: ]# df -h FilesystemSizeUsed Avail Capacity Mounted on /dev/mirror/gm0s1a496M373M 83M82%/ devfs 1.0K1.0K 0B 100%/dev /dev/mirror/gm0s1e496M 58M398M13%/tmp /dev/mirror/gm0s1f433G2.6G396G 1%/usr /dev/mirror/gm0s1d 13G 11G998M92%/var procfs4.0K4.0K 0B 100%/proc linprocfs 4.0K4.0K 0B 100%/usr/compat/linux/proc When I cd to /var and run a du -hs I get: # cd /var/ [r...@it05 /var]# du -hs * 2.0Kaccount 2.0Kagentx 6.0Kat 2.0Kaudit 12Kbackups 4.0Kcrash 6.0Kcron 168Mdb 2.0Kempty 2.0Kgames 2.0Kheimdal 18Klib 8.8Mlog 850Kmail 4.0Kmsgs 48Knamed 4.0Knet-snmp 2.0Kpreserve 54Krun 2.0Krwho 3.5Mspool 116Ktmp 24Kyp So, it seems that something is sucking up all the space but doesn't have a file descriptor on the file system, so du is not finding the file. Running lsof|grep /var I get: ... beam.smp 28398 ejabberd 10wVREG 0,93 3189523581 /var/log/ejabberd/erlang.log beam.smp 28398 ejabberd 11uVREG 0,93 9747130 /var/spool/ejabberd/LATEST.LOG beam.smp 28398 ejabberd 12wVREG 0,93 1117076867623582 /var (/dev/mirror/gm0s1d) beam.smp 28398 ejabberd 19uVREG 0,93 11922047140 /var/spool/ejabberd/offline_msg.DAT beam.smp 28398 ejabberd 20uVREG 0,93 680947142 /var/spool/ejabberd/private_storage.DAT beam.smp 28398 ejabberd 22uVREG 0,93 128259847148 /var/spool/ejabberd/pubsub_item.DAT beam.smp 28398 ejabberd 23uVREG 0,93 575247154 /var/spool/ejabberd/vcard.DAT beam.smp 28398 ejabberd 10wVREG 0,93 3189523581 /var/log/ejabberd/erlang.log beam.smp 28398 ejabberd 11uVREG 0,93 9747130 /var/spool/ejabberd/LATEST.LOG beam.smp 28398 ejabberd 12wVREG 0,93 1117076867623582 /var (/dev/mirror/gm0s1d) beam.smp 28398 ejabberd 19uVREG 0,93 11922047140 /var/spool/ejabberd/offline_msg.DAT beam.smp 28398 ejabberd 20uVREG 0,93 680947142 /var/spool/ejabberd/private_storage.DAT beam.smp 28398 ejabberd 22uVREG 0,93 128259847148 /var/spool/ejabberd/pubsub_item.DAT beam.smp 28398 ejabberd 23uVREG 0,93 575247154 /var/spool/ejabberd/vcard.DAT beam.smp 28398 ejabberd 10wVREG 0,93 3189523581 /var/log/ejabberd/erlang.log beam.smp 28398 ejabberd 11uVREG 0,93 9747130 /var/spool/ejabberd/LATEST.LOG beam.smp 28398 ejabberd 12wVREG 0,93 1117076867623582 /var (/dev/mirror/gm0s1d) beam.smp 28398 ejabberd 19uVREG 0,93 11922047140 /var/spool/ejabberd/offline_msg.DAT beam.smp 28398 ejabberd 20uVREG 0,93 680947142 /var/spool/ejabberd/private_storage.DAT beam.smp 28398 ejabberd 22uVREG 0,93 128259847148 /var/spool/ejabberd/pubsub_item.DAT beam.smp 28398 ejabberd 23uVREG 0,93 575247154 /var/spool/ejabberd/vcard.DAT beam.smp 28398 ejabberd 10wVREG 0,93 3189523581 /var/log/ejabberd/erlang.log beam.smp 28398 ejabberd 11uVREG 0,93 9747130 /var/spool/ejabberd/LATEST.LOG beam.smp 28398 ejabberd 12wVREG 0,93 1117076867623582 /var (/dev/mirror/gm0s1d) beam.smp 28398 ejabberd 19uVREG 0,93 11922047140 /var/spool/ejabberd/offline_msg.DAT beam.smp 28398 ejabberd 20uVREG 0,93 680947142 /var/spool/ejabberd/private_storage.DAT beam.smp 28398 ejabberd 22uVREG 0,93 128259847148 /var/spool/ejabberd/pubsub_item.DAT beam.smp 28398 ejabberd 23uVREG 0,93 575247154 /var/spool/ejabberd/vcard.DAT beam.smp 28398 ejabberd 10wVREG 0,93 3189523581 /var/log/ejabberd/erlang.log beam.smp 28398 ejabberd 11uVREG 0,93 9747130 /var/spool/ejabberd/LATEST.LOG beam.smp 28398 ejabberd 12wVREG 0,93 1117076867623582 /var (/dev/mirror/gm0s1d) beam.smp 28398 ejabberd 19uVREG 0,93 11922047140 /var/spool/ejabberd/offline_msg.DAT beam.smp 28398 ejabberd 20uVREG
Filesystem problem
Hi. I have been experencing some filesystem problems for the last month or so. I was running 4.8-STABLE and updated to 5.1-RELEASE-p2. While I was running 4.8 and I tried to run a command that required hard disk activity, the process would 'hang' and I would no longer be able to ssh or telnet in. I would get stuck after typing in my login. Running 5.1 is a different story. I did a clean install of 5.1-RELEASE and cvsup'd to -p2. Every time I do this, it's great for a day or so then it acts up. Before after it started, even if I rebooted it would immediately start up. On 5.1, it is only hanging for that process and everything else is fine. I can still login, webserver responds, etc. Here is a little info: FreeBSD devel.neoninternet.net 5.1-RELEASE-p2 FreeBSD 5.1-RELEASE-p2 #0: Sat Aug 23 20:12:41 PDT 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SLURPEE i386 CPU: AMD Athlon(tm) XP 2600+ (2086.51-MHz 686-class CPU) real memory = 1073676288 (1023 MB) ad0: 117246MB Maxtor 6Y120P0 [238216/16/63] at ata0-master UDMA133 root 1173 0.0 0.1 1436 916 p3 D+6:38PM 0:00.00 man vmstat root784 0.0 0.1 752 636 d0 D 4:34PM 0:00.02 make all DIRPRFX=i386/libi386/ root847 0.0 0.0 312 212 d0 D 4:34PM 0:00.00 (cc) root848 0.0 0.3 4104 3488 d0 D 4:34PM 0:00.01 (cc1) root849 0.0 0.1 928 668 d0 D 4:34PM 0:00.00 /usr/bin/as -o comconsole.o - last pid: 1252; load averages: 0.00, 0.00, 0.00 up 0+02:37:22 19:04:48 64 processes: 1 running, 63 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 34M Active, 23M Inact, 38M Wired, 204K Cache, 22M Buf, 906M Free Swap: 2048M Total, 2048M Free devel# vmstat procs memory pagedisks faults cpu r b w avmfre flt re pi po fr sr ad0 da0 in sy cs us sy id 1 7 0 144612 928056 16 0 0 0 9 0 0 0 3310 254 0 0 100 Anyone have any suggestions? I can not control-C out of 'man vmstat'. While doing 'make' in /usr/src/sys/boot it was hanging on as, when I restarted it, it got to i386/libi386 and will not do anything else. I'm running that through serial console, it let me ^C out of that. I tried going into single user mode and running umount, now it just sits there and I can't ^C. I have no ideas, this was all working yesterday!! :-) Any ideas on what else to check or other helpful hints would help bunches. Thanks, Kevin __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
filesystem problem resolved - /sbin/mount was causing it
Hi Everybody The problem cleared out. I now know what, but not why :) For those of you interested. I have a 2nd disk in the machine (ad3) which has a backup parition (ad3f). This partition is mounted to a mountpoint (guess: in root) to /mnt/vol1. For strange reasons (who knows why?) mount fails (see below), therefor the volume gets not mounted and the backup sits in the mountpoint directory, filling up... /. Btw: I moved all /modules /sbin /bin to their right places back. Now the mount fails as showed here. The backup partition is not mountalbe, but another, on the same disk, is... caramba# mount /dev/ad3f /mnt/vol1 mount: /dev/ad3f: Operation not permitted caramba# mount /dev/ad3f /backup/slice1 mount: /dev/ad3f: Operation not permitted caramba# here another partition: caramba# mount /dev/ad0s1a on / (ufs, local) /dev/ad0s1e on /usr (ufs, local) /dev/ad0s1g on /usr/www (ufs, local) /dev/ad0s1f on /var (ufs, local) procfs on /proc (procfs, local) /dev/ad3e on /mnt/vol1 (ufs, local) caramba# umount /mnt/vol1/ caramba# the disklabel entry: caramba# disklabel ad3 # /dev/ad3c: type: ESDI disk: ad3s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 31206 sectors/unit: 31456593 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 314565930unused0 0 # (Cyl.0 - 31206*) e: 419430404.2BSD 1024 819216 # (Cyl.0 - 4161*) f: 12582912 41943044.2BSD 1024 819216 # (Cyl. 4161*- 16644*) g: 12582912 167772164.2BSD 1024 819216 # (Cyl. 16644*- 29127*) h: 2096465 293601284.2BSD 1024 819216 # (Cyl. 29127*- 31206*) caramba# -- no, i can stop backups for the moment, or repoint them to another partition, e.g. ad3g, but why does mount not work on that respectively give operation not permitted? Thanks Arie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystem problem resolved - /sbin/mount was causing it
Arie J. Gerszt writes: Hi Everybody The problem cleared out. I now know what, but not why :) For those of you interested. I have a 2nd disk in the machine (ad3) which has a backup parition (ad3f). This partition is mounted to a mountpoint (guess: in root) to /mnt/vol1. For strange reasons (who knows why?) mount fails (see below), therefor the volume gets not mounted and the backup sits in the mountpoint directory, filling up... /. Btw: I moved all /modules /sbin /bin to their right places back. Now the mount fails as showed here. The backup partition is not mountalbe, but another, on the same disk, is... caramba# mount /dev/ad3f /mnt/vol1 mount: /dev/ad3f: Operation not permitted caramba# mount /dev/ad3f /backup/slice1 mount: /dev/ad3f: Operation not permitted caramba# here another partition: caramba# mount /dev/ad0s1a on / (ufs, local) /dev/ad0s1e on /usr (ufs, local) /dev/ad0s1g on /usr/www (ufs, local) /dev/ad0s1f on /var (ufs, local) procfs on /proc (procfs, local) /dev/ad3e on /mnt/vol1 (ufs, local) caramba# umount /mnt/vol1/ caramba# the disklabel entry: caramba# disklabel ad3 # /dev/ad3c: type: ESDI disk: ad3s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 31206 sectors/unit: 31456593 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 314565930unused0 0 # (Cyl.0 - 31206*) e: 419430404.2BSD 1024 819216 # (Cyl.0 - 4161*) f: 12582912 41943044.2BSD 1024 819216 # (Cyl. 4161*- 16644*) g: 12582912 167772164.2BSD 1024 819216 # (Cyl. 16644*- 29127*) h: 2096465 293601284.2BSD 1024 819216 # (Cyl. 29127*- 31206*) caramba# -- no, i can stop backups for the moment, or repoint them to another partition, e.g. ad3g, but why does mount not work on that respectively give operation not permitted? Thanks Arie Hi, Are you trying to mount the backup volume as root? By default only root is allowed to mount and unmount volumes. Also check if the mount pouint is having write permissions when you try to mount the volume. Subhro Sankha Kar IIIT-Calcutta ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
