search for: ad4s1

...nd forgot to disable it. Unsurprisingly my /var partition maxed out. To correct this, I disabled the logging and deleted the (approx 240 MB) samba log file. Strangely I still had a full /var partition. Running df gave me: SRV04# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad4s1a 253678 55830 177554 24% / devfs 1 1 0 100% /dev /dev/ad4s1e 253678 16 233368 0% /tmp /dev/ad4s1f 235212398 46345500 170049908 21% /usr /dev/ad4s1d 253678 225076 8308 96% /var I ran du -hc on /var which gave...

Hi. rsync 3.0.8 FreeBSD RELENG_4 i386. rsync -Haxi --delete /.../ /.../ The first pathspec above (residing on zz, a full filesystem) is: /vvvv/wwww/xxxx/zz/ The second pathspec above (residing on yyy, an empty filesystem) is: /vvvv/wwww/xxxx/yyy/zz/ It's obviously a 'copy everything over' operation. I've had to obfuscate the pathnames, however the exact pathlength throughout

...s hosting that service anyway? And now for the question.. I have a test server that is being used to test a 4.4-REL to 4.8-STABLE upgrade, and I've found the system will no longer boot unless I load a saved 4.4-REL kernel. The error I get is along the lines of: Mounting root from ufs:/dev/ad4s1a Root mount failed: 16 At first I got this error using a custom kernel configuration known as WWW, but after getting this error I built a new kernel based on GENERIC: # cd /usr/src # make update # make buildkernel # make installkernel # reboot Per /usr/src/UPDATING there was a change in the ATA...

...l me if I can recover some how? or should I just rebuild the array? or is one of my disks physically bad? Detects all 7 drives (1 10gig plus 6 20gigs) vinum: loaded vinum: reading configuration from /dev/ad6s1e vinum: updating configuration from /dev/ad5s1e vinum: updating configuration from /dev/ad4s1e vinum: updating configuration from /dev/ad2s1e vinum: updating configuration from /dev/ad3s1e vinum: updating configuration from /dev/ad1s1e Warning: defective objects P array.p0 S State: corrupt Subdisks: 6 Size: 111 GB S array.po.s4 State: stale D: d5 Size: 18 GB swapon: adding /dev/ad0...

Hi, I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which I'd like to try installing FreeBSD. I've already failed to make 7.0 work on this box and was wondering if you have information about the behavior of the upcoming 7.1 on this hardware. I've been following the "HT1000 chipset errata saga" thread, and the commits by sos@ to CVS (around Jan 2008), but have

...f the nfs server. The lack of logout after the 15:22:54 one suggests that this was the point that the file server went offline. The only directory that was mounted at that time was in /export (/dev/mirror/gm1a): alson@damaged:~$ gmirror status Name Status Components mirror/gm0 DEGRADED ad4s1 mirror/gm1 COMPLETE ad8s1 ad10s1 The server had been up for about 250 days with similar (and usually significantly heavier) load with 6.2-STABLE before the upgrade. The evening after the crash, I received the following message from smartmontools (not sure if it's relate...

...sec acd0: DVDR <PLEXTOR DVDR PX-740A/1.01> at ata0-master UDMA33 ad4: 286168MB <Seagate ST3300622AS 3.AAE> at ata2-master SATA150 ad6: 286168MB <Seagate ST3300622AS 3.AAE> at ata3-master SATA150 GEOM_MIRROR: Device gm0s1 created (id=3185843744). GEOM_MIRROR: Device gm0s1: provider ad4s1 detected. GEOM_MIRROR: Device gm0s1: provider ad6s1 detected. GEOM_MIRROR: Device gm0s1: provider ad6s1 activated. GEOM_MIRROR: Device gm0s1: provider ad4s1 activated. GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. SMP: AP CPU #1 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: <PLEXT...

...13,0x3018-0x301f,0x3014-0x3017,0x3020-0x3027 mem 0xf4200000-0xf4203fff irq 11 at device 7.0 on pci2 The fdisk entry for the disk is: /dev/ad4: 317632 cyl 16 hd 63 sec Part Start Size Type Flags 1: 63 320172993 0xa5 0x80 The disklabel reads: # /dev/ad4s1c: ... 8 partitions: # size offset fstype [fsize bsize bps/cpg] b: 265 0 swap # (Cyl. 0 - 0*) c: 320172993 0 unused 0 0 # (Cyl. 0 - 317631*) e: 320172728 265 vinum...

...NEW (device gm0). GEOM_MIRROR[1]: Device gm0: provider ad4 detected. ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad8: 476940MB <SAMSUNG HD501LJ CR100-13> at ata4-master SATA300 ad8: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM_MIRROR[2]: Tasting ad4s1. GEOM_MIRROR[2]: Tasting ad4a. GEOM_MIRROR[2]: Tasting ad4c. GEOM: new disk ad8 ad8: nVidia check1 failed ad8: Adaptec check1 failed ad8: LSI (v3) check1 failed GEOM_MIRROR[2]: Tasting ad8. ad8: LSI (v2) check1 failed magic: GEOM::MIRROR version: 4 name: gm0 mid: 2403671335...

A while back, I submitted a patch for PR kern/124621, which allows the mounting of an ext2(3) filesystem created with an inode size other than 128. The e2fsprogs' default is now 256, so file systems created on newer Linux distributions or with the port will not be mountable. I was hopeful this would get committed in time for 7.1-RELEASE (and 6.4-RELEASE), however the PR remains open. If

Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190 Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix whatever to the questions posed as fsck runs. What does this all mean? Thanks, -Clint -- This message has...

...sec acd0: DVDR <PLEXTOR DVDR PX-740A/1.01> at ata0-master UDMA33 ad4: 286168MB <Seagate ST3300622AS 3.AAE> at ata2-master SATA150 ad6: 286168MB <Seagate ST3300622AS 3.AAE> at ata3-master SATA150 GEOM_MIRROR: Device gm0s1 created (id=3185843744). GEOM_MIRROR: Device gm0s1: provider ad4s1 detected. GEOM_MIRROR: Device gm0s1: provider ad6s1 detected. GEOM_MIRROR: Device gm0s1: provider ad6s1 activated. GEOM_MIRROR: Device gm0s1: provider ad4s1 activated. GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. SMP: AP CPU #1 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: <PLEXT...

...t;LITE-ON DVDRW SHW-160P6S/PS08> at ata0-master UDMA33 ad4: 238475MB <HDT722525DLA380 V44OA9BA> at ata2-master SATA300 ad8: 157066MB <HDT722516DLA380 V43OA91A> at ata4-master SATA300 ad10: 157066MB <HDT722516DLA380 V43OA91A> at ata5-master SATA300 GEOM_LABEL: Label for provider ad4s1a is ufsid/47d2f5b0f707e35a. GEOM_LABEL: Label for provider ad4s1d is ufsid/47d2f5b415e377aa. GEOM_JOURNAL: Journal 2799764387: ad4s1e contains journal. GEOM_LABEL: Label for provider ad4s1f is ufsid/47d2f5b95c287bb2. GEOM_JOURNAL: Journal 2799764387: ad4s1g contains data. GEOM_JOURNAL: Journal ad4s...