daily otput: rejected mail hosts?
I see in the daily output: Checking for rejected mail hosts: 172 553 check_mail system.mail exist 129 553 check_mail tsvpt014.vpt.co.uk exist 43 553 check_mail unix.dedicated.com.tr exist 43 553 check_mail ubs.net exist 43 553 check_mail localhost.localdomain exist 43 553 check_mail journal-cfp.org exist 43 553 check_mail italiasito.it exist What is that about? Is this described somewhere in sendmail manuals? Thanks Anton ___ 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
3 TB disk troubles
I recently bought a 3 TB external hard drive. I attached it to the Firewire (400) bus and waited for my 8.2-STABLE i386 system to recognize it. After a small flurry of Firewire protocol messages, the kernel eventually said, Feb 12 23:35:42 hellas kernel: da2 at sbp0 bus 0 scbus0 target 1 lun 0 Feb 12 23:35:42 hellas kernel: da2: Initio INIC-1615P 0101 Fixed Direct Access SCSI-0 device Feb 12 23:35:42 hellas kernel: da2: 50.000MB/s transfers Feb 12 23:35:42 hellas kernel: da2: 2861588MB (5860533167 512 byte sectors: 255H 63S/T 364801C) So far, so good, I thought. Next I tried to use gpart(8) to set up a partition table. However, gpart, gpte (from sysutils/gpte), diskinfo(8), et al. only see the device as a 2 TB drive. hellas# diskinfo -v /dev/da2 /dev/da2 512 # sectorsize 2199023253504 # mediasize in bytes (2T) 4294967292 # mediasize in sectors 0 # stripesize 0 # stripeoffset 267349 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. # Disk ident. hellas# I have searched the archives of this list and several others, but haven't found anything helpful. This disk is *not* intended as a boot disk, just data storage. Is there any hope of using its full capacity? Or have I effectively bought an overpriced 2 TB drive? Please Cc: me directly in any replies because I am subscribed to the digest form of this list and would like to see responses without having to wait up to 24 hours. :-) Thanks in advance for any help! Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at mp.cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ 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: 3 TB disk troubles
On Thu, 14 Feb 2013 13:21:38 +0100 Joar Jegleim joar.jegl...@gmail.com wrote: I could be completely off mark here, but does that external drive have eSata too ? No, it only has Firewire 400 and USB 2.0 sockets. Your problem resembles a lot something I struggled with a while ago. I'd bought an external hd case + a 3TB drive for my girlfriend , the external hd case supported eSATA and usb . I had a lot of problems when connecting that 3TB drive to my laptop via usb (I didn't have eSATA), the drive showed up as only 2TB . It turned out that the external drive case required to be connected via eSATA for +2TB drives, the manual said so, I had only forgotten about that . Unfortunately, mine did not come with a manual. :-( I suppose I could try it on a USB 2.0 port to see if that makes any difference. Via eSATA the drive was recognized as 3TB, I think the 'problem' was OS agnostic, since the same happened on my girlfriends mac. The confusing thing is that the kernel says it's a 3 TB device, but the utility programs say otherwise. Thanks for your reply, though. I may have to take the device back to the store I bought it and ask them to demonstrate to me that it actually works for them as a 3 TB drive. Sigh. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at mp.cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ 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
Why scf (sfcd) monitoring sometimes doesn't work
Hello, I found fsc (http://www.freshports.org/sysutils/fsc/) to be extremely useful. Unfortunately, I can't get some services to be monitored, fscadm enable just failes with Could not monitor service. I don't know how kqueue interaction is working, so I can't guess why some services can be monitored fine and others not. How can I start finding out what goes wrong? How does the rc-name play into that role? Thanks, -Harry signature.asc Description: OpenPGP digital signature
Why fsc (fscd) monitoring sometimes doesn't work [Was: Re: Why scf (sfcd) monitoring sometimes doesn't work]
schrieb Harald Schmalzbauer am 14.02.2013 13:34 (localtime): Hello, I found fsc (http://www.freshports.org/sysutils/fsc/) to be extremely useful. Unfortunately, I can't get some services to be monitored, fscadm enable just failes with Could not monitor service. I don't know how kqueue interaction is working, so I can't guess why some services can be monitored fine and others not. How can I start finding out what goes wrong? How does the rc-name play into that role? Sorry for the ugly typo in the topic! signature.asc Description: OpenPGP digital signature
Re: setting MIBs on a per jail bases
schrieb Fbsd8 am 06.02.2013 17:57 (localtime):
Fleuriot Damien wrote:
Running 8.3 here and the answer is no.
On Feb 6, 2013, at 5:39 PM, Fbsd8 fb...@a1poweruser.com wrote:
Is there a way to set these MIBs
on a per jail bases?
allow.mount.nullfs
allow.raw_sockets
cpuset.id
securelevel
Rereading the man jail for 9.1 talks about securelevel as a jail
parammeter. So correct me if I an wrong. All the security.jail.param.*
MIBs are set in rc.conf or /etc/jail.conf file on a per jail bases by
changing the word parm to the jailname?
This applies to jail.conf(5).
That's a entirely new way to handle jails in FreeBSD 9.1. Very nice, but
not included in rc.d.
If you want to keep the traditional way running jails, I made a patch
some time ago to control more per-jail tunables.
Here you can donwload it for -9:
ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools/local-patches/src/jail-allow-selectables.patch_9
That also irons some ip configuration cosmetics, see defaults/rc.conf.
If you want to give the new jail(8) and jail.conf capabilities a try,
here's like I use it with vnet (vimage, virtual per-jail-network stack):
Compile a kernel with options VIMAGE
remove # keyword nojail in jail's etc/rc.d/netif and routing (if you
want to set IP addresses inside the jail)
And here's the corresponding jail.conf:
###
exec.start = /bin/sh /etc/rc;
exec.stop = /bin/sh /etc/rc.shutdown sleep 2;
exec.clean;
allow.mount;
allow.mount.devfs;
allow.set_hostname;
mount.devfs;
devfs_ruleset=4;
# Dynamic wildcard parameter:
# Base the path off the jail name.
path = /.jail.$name;
mount.fstab=/etc/fstab.$name;
yourname {
mount;
name = inno;
# host.hostname = .your hostname.net; but also set inside the
jail along with network setup
vnet = new;
vnet.interface = jbb$name;
}
###
You can add allow.raw_sockets anywhere.
But with vnet, you don't need that any more.
Just to point you into the right direction.
-Harry
signature.asc
Description: OpenPGP digital signature
Question about port: net/linux-f10-openldap
When I install net/linux-f10-openldap (required by www/linux-f10- flashplugin), it installs a dangling symlink; i.e. /compat/linux/etc/ openldap. I realise of course that this is a rather trivial question, but should it be so? ___ 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: setting MIBs on a per jail bases
schrieb Harald Schmalzbauer am 14.02.2013 14:18 (localtime): schrieb Fbsd8 am 06.02.2013 17:57 (localtime): Fleuriot Damien wrote: Running 8.3 here and the answer is no. On Feb 6, 2013, at 5:39 PM, Fbsd8 fb...@a1poweruser.com wrote: Is there a way to set these MIBs on a per jail bases? allow.mount.nullfs allow.raw_sockets cpuset.id securelevel Rereading the man jail for 9.1 talks about securelevel as a jail parammeter. So correct me if I an wrong. All the security.jail.param.* MIBs are set in rc.conf or /etc/jail.conf file on a per jail bases by changing the word parm to the jailname? This applies to jail.conf(5). That's a entirely new way to handle jails in FreeBSD 9.1. Very nice, but not included in rc.d. If you want to keep the traditional way running jails, I made a patch some time ago to control more per-jail tunables. Here you can donwload it for -9: ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools/local-patches/src/jail-allow-selectables.patch_9 That also irons some ip configuration cosmetics, see defaults/rc.conf. See also http://docs.freebsd.org/cgi/getmsg.cgi?fetch=686783+0+archive/2010/freebsd-stable/20100704.freebsd-stable -Harry signature.asc Description: OpenPGP digital signature
Re: 3 TB disk troubles
--On February 14, 2013 6:33:31 AM -0600 Scott Bennett benn...@cs.niu.edu wrote: The confusing thing is that the kernel says it's a 3 TB device, but the utility programs say otherwise. Thanks for your reply, though. I may have to take the device back to the store I bought it and ask them to demonstrate to me that it actually works for them as a 3 TB drive. Sigh. What utilities are you referring to? If it's fdisk and bsdlabel, those can only see 2TB no matter how big the disk is. What does gpart show tell you? Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at mp.cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ 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 -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: 3 TB disk troubles
On Thu, 14 Feb 2013, Scott Bennett wrote: The confusing thing is that the kernel says it's a 3 TB device, but the utility programs say otherwise. There are more than a few SATA to USB adapters that are not capable of dealing with larger devices. I've seen at least one that could not handle a 1T drive. Now that larger drives are becoming more common, the limits are often shown on the device box or description. The kernel may still identify the device correctly, possibly with different capacity detection. As mentioned, ESATA or just bypassing the SATA/USB/Firewire adapter and connecting directly to the drive should give the full capacity. ___ 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: about unatteneded installation
Hi Devin, On 12/20/12 1:10 PM, Devin Teske devin.te...@fisglobal.com wrote: For now, people that prefer sysinstall can use my FreeBSD Druid pre-built install media: For 9.0: http://sourceforge.net/projects/druidbsd/files/FreeBSD-9.0_Druid-1.0b60.iso/download For 8.3: http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/download As for 10.0 (when it comes out), expect bsdinstall to surpass sysinstall (in many many great ways) in every way (unlike the current status in 9.x). I had begun evaluating FreeBSD Druid and DruidBSD, but was sidetracked with a different project. I'm hoping to return to this in the coming weeks. Having said that, I am wondering what disk partition utilities FreeBSD Druid/DruidBSD use when installing 9.x. Is it using fdisk/bsdlabel or gpart? -- Take care Rick Miller ___ 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: about unatteneded installation
On Thu, 14 Feb 2013, Rick Miller wrote:
Hi Devin,
On 12/20/12 1:10 PM, Devin Teske devin.te...@fisglobal.com wrote:
For now, people that prefer sysinstall can use my FreeBSD Druid pre-built
install media:
For 9.0:
http://sourceforge.net/projects/druidbsd/files/FreeBSD-9.0_Druid-1.0b60.iso/download
For 8.3:
http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/download
As for 10.0 (when it comes out), expect bsdinstall to surpass sysinstall
(in many many great ways) in every way (unlike the current status in 9.x).
I had begun evaluating FreeBSD Druid and DruidBSD, but was sidetracked
with a different project. I'm hoping to return to this in the coming
weeks. Having said that, I am wondering what disk partition utilities
FreeBSD Druid/DruidBSD use when installing 9.x. Is it using
fdisk/bsdlabel or gpart?
Hi Rick,
No worries on time lapse. In fact, I had been needing to get back to you on
assuaging those 4 failed patch hunks on your sysinstall work.
FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What
does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination
of:
+ libdisk ( see, for example, Set_Boot_Mgr(3) within case 'W' of switch
(toupper(key)) in function diskPartition() of file
stable/9/usr.sbin/sysinstall/disks.c lines 630-693)
http://svnweb.freebsd.org/base/stable/9/usr.sbin/sysinstall/disks.c?revision=225736view=markup
and ...
+ phk code (see, for example, slice_wizard() function in file
stable/9/usr.sbin/sysinstall/wizard.c lines 65-201, in-use for case '|' of
the same switch above, same function, lines 695-707 of
stable/9/usr.sbin/sysinstall/disks.c)
http://svnweb.freebsd.org/base/stable/9/usr.sbin/sysinstall/disks.c?revision=225736view=markup
http://svnweb.freebsd.org/base/stable/9/usr.sbin/sysinstall/wizard.c?revision=225736view=markup
But wait, there's more...
The FreeBSD 9 version of my FreeBSD Druid has a patch to perform (only when
doing automated/scripted installs):
gpart -F destroy ${dest_disk}
The reason for this is that if you, say for example, were to try the bsdinstall
based media and then want to try sysinstall based media, you're actually
prevented from re-formatting that disk into a usable MBR layout until you
destroy the GPT backup label stored at the end of the disk.
So the FreeBSD Druid for 9.x is basically the same as for 8.x with an
additional twist, it has gpart in the mfsroot so that it can do a destroy on
the GPT backup data before formatting the disk in automated installations (this
destroy command is not done for non-scripted installs).
You can see the code here:
http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/freebsd/menu/etc/all_install?r1=1.2r2=1.3
http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/freebsd/menu/etc/all_install?revision=1.3view=markup
--
Devin
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
___
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: 3 TB disk troubles
On 14 Feb 2013, at 17:01, Warren Block wbl...@wonkity.com wrote: On Thu, 14 Feb 2013, Scott Bennett wrote: The confusing thing is that the kernel says it's a 3 TB device, but the utility programs say otherwise. There are more than a few SATA to USB adapters that are not capable of dealing with larger devices. I've seen at least one that could not handle a 1T drive. Now that larger drives are becoming more common, the limits are often shown on the device box or description. The kernel may still identify the device correctly, possibly with different capacity detection. As mentioned, ESATA or just bypassing the SATA/USB/Firewire adapter and connecting directly to the drive should give the full capacity. I might be completely off here but, what about trying it over FireWire on a x64 box, as opposed to his 32bit 8.2 ? ___ 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: about unatteneded installation
On Thu, Feb 14, 2013 at 12:34 PM, Teske, Devin devin.te...@fisglobal.com wrote: On Thu, 14 Feb 2013, Rick Miller wrote: No worries on time lapse. In fact, I had been needing to get back to you on assuaging those 4 failed patch hunks on your sysinstall work. FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination of: I anticipated this. I am under the impression one cannot force proper slice alignment on 4K sector drives with sysinstall (see http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html). Is it safe to assume that this also applies to 9.x when utilizing sysinstall based installer? -- Take care Rick Miller ___ 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: 3 TB disk troubles
I recently bought a 3 TB external hard drive. I attached it to the Firewire (400) bus and waited for my 8.2-STABLE i386 system to recognize it. After a small flurry of Firewire protocol messages, the kernel eventually said, Feb 12 23:35:42 hellas kernel: da2 at sbp0 bus 0 scbus0 target 1 lun 0 Feb 12 23:35:42 hellas kernel: da2: Initio INIC-1615P 0101 Fixed Direct Access SCSI-0 device Feb 12 23:35:42 hellas kernel: da2: 50.000MB/s transfers Feb 12 23:35:42 hellas kernel: da2: 2861588MB (5860533167 512 byte sectors: 255H 63S/T 364801C) So far, so good, I thought. Next I tried to use gpart(8) to set up a partition table. However, gpart, gpte (from sysutils/gpte), diskinfo(8), et al. only see the device as a 2 TB drive. hellas# diskinfo -v /dev/da2 /dev/da2 512 # sectorsize 2199023253504 # mediasize in bytes (2T) 4294967292 # mediasize in sectors 0 # stripesize 0 # stripeoffset 267349 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. # Disk ident. hellas# I have searched the archives of this list and several others, but haven't found anything helpful. This disk is *not* intended as a boot disk, just data storage. Is there any hope of using its full capacity? Or have I effectively bought an overpriced 2 TB drive? Please Cc: me directly in any replies because I am subscribed to the digest form of this list and would like to see responses without having to wait up to 24 hours. :-) Thanks in advance for any help! Scott Bennett, Comm. ASMELG, CFIAG There is Rod Smith's gdisk, a gpt counterpart of fdisk. http://rodsbooks.com/gdisk/ and available in FreeBSD ports collection, one version (0.8.5) behind Rod's current version 0.8.6. This works for me. Tom ___ 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: about unatteneded installation
-Original Message- From: vrwmil...@gmail.com [mailto:vrwmil...@gmail.com] On Behalf Of Rick Miller Sent: Thursday, February 14, 2013 10:39 AM To: Teske, Devin Cc: FreeBSD Questions Subject: Re: about unatteneded installation On Thu, Feb 14, 2013 at 12:34 PM, Teske, Devin devin.te...@fisglobal.com wrote: On Thu, 14 Feb 2013, Rick Miller wrote: No worries on time lapse. In fact, I had been needing to get back to you on assuaging those 4 failed patch hunks on your sysinstall work. FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination of: I anticipated this. I am under the impression one cannot force proper slice alignment on 4K sector drives with sysinstall (see http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html). Is it safe to assume that this also applies to 9.x when utilizing sysinstall based installer? As previously mentioned, the FreeBSD Druid for FreeBSD 9.x contains gpart in the mfsroot. To make this work under sysinstall, you'd essentially tell sysinstall to use what's already there (and by already there, I mean have a script pre-create the partition layout with gpart prior to installation). There are places (like the all_install script) in the FreeBSD Druid that would make this a simple proposition, but I'm afraid that the better solution (according to the article) is to use a true 4K-only drive (the article mentions that the problem only comes into play with drives that advertise both 512 and 4K sector sizes). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: about unatteneded installation
On Thu, 14 Feb 2013, dte...@freebsd.org wrote: -Original Message- From: vrwmil...@gmail.com [mailto:vrwmil...@gmail.com] On Behalf Of Rick Miller Sent: Thursday, February 14, 2013 10:39 AM To: Teske, Devin Cc: FreeBSD Questions Subject: Re: about unatteneded installation On Thu, Feb 14, 2013 at 12:34 PM, Teske, Devin devin.te...@fisglobal.com wrote: On Thu, 14 Feb 2013, Rick Miller wrote: No worries on time lapse. In fact, I had been needing to get back to you on assuaging those 4 failed patch hunks on your sysinstall work. FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination of: I anticipated this. I am under the impression one cannot force proper slice alignment on 4K sector drives with sysinstall (see http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html). Is it safe to assume that this also applies to 9.x when utilizing sysinstall based installer? As previously mentioned, the FreeBSD Druid for FreeBSD 9.x contains gpart in the mfsroot. To make this work under sysinstall, you'd essentially tell sysinstall to use what's already there (and by already there, I mean have a script pre-create the partition layout with gpart prior to installation). Yes, but neither fdisk(8) nor gpart(8) can align slices to arbitrary (aligned) locations. They will always be aligned to CHS values, equivalent to using -a63 in gpart. gpart(8) can align FreeBSD partitions inside a slice, though. ___ 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
Is this an SSD problem or a controller problem?
This error has shown up at boot up, and then again trying to fire up smartd.conf. (aprobe0:ata2:0:0:0): SETFEATURES DISABLE SATA FEATURE. ACB: ef 90 00 00 00 40 00 00 00 00 02 00 (aprobe0:ata2:0:0:0): CAM status: ATA Status Error (aprobe0:ata2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (aprobe0:ata2:0:0:0): RES: 51 04 00 00 00 00 00 00 00 02 00 (aprobe0:ata2:0:0:0): Retrying command (aprobe0:ata2:0:0:0): SETFEATURES DISABLE SATA FEATURE. ACB: ef 90 00 00 00 40 00 00 00 00 02 00 (aprobe0:ata2:0:0:0): CAM status: ATA Status Error (aprobe0:ata2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (aprobe0:ata2:0:0:0): RES: 51 04 00 00 00 00 00 00 00 02 00 (aprobe0:ata2:0:0:0): Error 5, Retries exhausted The device is an SSD on ada15. smartctl 6.0 2012-10-10 r3643 [FreeBSD 9.1-RELEASE amd64] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Indilinx Everest/Martini based SSDs Device Model: OCZ-VERTEX4 Serial Number:OCZ-7T2T10Q1P4294S68 LU WWN Device Id: 5 e83a97 7039f0a47 Firmware Version: 1.5 User Capacity:128,035,676,160 bytes [128 GB] Sector Size: 512 bytes logical/physical Rotation Rate:Solid State Device Device is:In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is:Thu Feb 14 14:16:00 2013 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled dmesg | grep ada15 ada15 at ata2 bus 0 scbus12 target 0 lun 0 ada15: OCZ-VERTEX4 1.5 ATA-9 SATA 3.x device ada15: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes) ada15: 122104MB (250069680 512 byte sectors: 16H 63S/T 16383C) ada15: Previously was known as ad28 smartctl -a /dev/ada15 smartctl 6.0 2012-10-10 r3643 [FreeBSD 9.1-RELEASE amd64] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Indilinx Everest/Martini based SSDs Device Model: OCZ-VERTEX4 Serial Number:OCZ-7T2T10Q1P4294S68 LU WWN Device Id: 5 e83a97 7039f0a47 Firmware Version: 1.5 User Capacity:128,035,676,160 bytes [128 GB] Sector Size: 512 bytes logical/physical Rotation Rate:Solid State Device Device is:In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is:Thu Feb 14 16:09:21 2013 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. Total time to complete Offline data collection:(0) seconds. Offline data collection capabilities:(0x1d) SMART execute Offline immediate. No Auto Offline data collection support. Abort Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x00) Error logging NOT supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 0) minutes. Extended self-test routine recommended polling time:( 0) minutes. SMART Attributes Data Structure revision number: 18 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x 006 000 000Old_age Offline - 6 3 Spin_Up_Time0x 100 100 000Old_age Offline - 0 4 Start_Stop_Count0x 100 100 000Old_age Offline - 0 5 Reallocated_Sector_Ct 0x 100 100 000Old_age Offline - 0 9 Power_On_Hours 0x 100 100 000Old_age Offline - 3334 12 Power_Cycle_Count 0x 100 100 000
Re: building custom kernel on -current: unknown option COMPAT_LINUX
On Saturday, February 09, 2013 10:01:25 pm ill...@gmail.com wrote: On 9 February 2013 20:26, Anton Shterenlikht me...@bristol.ac.uk wrote: I removed COMPAT_LINUX, and only left options COMPAT_43 options COMPAT_LINUX32 From /usr/src/sys/amd64/conf/NOTES (9.1-RELEASE): # Enable Linux ABI emulation #XXX#optionsCOMPAT_LINUX # Enable 32-bit Linux ABI emulation (requires COMPAT_43 and COMPAT_FREEBSD32) options COMPAT_LINUX32 I think I first ran up against this when I moved to 9.0 some time ago, but yes, amd64 uses a different kernel config option than i386 for linux compat. I tend to leave it as a module load it if I perchance need it. This also allows rebuilding reloading the modules without a reboot, should it need it. The modules seems to build fine without having to fiddle about with kernel config jiggerypokey. COMPAT_LINUX will work on amd64 eventually and will be used for 64-bit Linux binaries (COMPAT_LINUX32 is to run Linux/i386 binaries on FreeBSD/amd64). -- John Baldwin ___ 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
Installing Matlab
I was wondering if anyone has had any recent (or not-so-recent) experience installing Matlab on FreeBSD/PC-BSD? (Yes, I know about octave.) I'm not entirely new to *nix, but I'm novice enough that I can't seem to get this to work. Perhaps the shortest and simplest solution would be if Mathworks own installer would function, but that runs as a Java Web Start application, and I can't seem to get that working in Opera, Firefox, or Konqueror. The automatic rout having failed, I've downloaded the files manually, and I've tried to run the install script; however, it's failed as well. I found this site: http://matrossi.blogspot.com/2011/08/installing-matlab-2011a-on-freebsd.html, which claims installation instructions for PC-BSD8.2 boiling down to: open up the shell scripts and take /bin/sh -- /compat/linux/bin/sh. Well, that seems to help a bit, but it also fails because the install script determines my architecture to be x68, while the downloads are for (what they call) a64. (My system is indeed a 64-bit system. Perhaps the above instructions were for an x86 system.) I feel like if I could modify the install script sufficiently, the install would work. My bash scripting is weak, though, and I worry about screwing up my system and/or the installation. There are only a few functions in there that are looking for architecture type, usually with the output from uname. I think fixing those would work...? Could anyone help me get past this point? Thanks in advance! And please, if there's any info I can provide that would be helpful, please just let me know. Output of uname -a: FreeBSD pcbsd-8517 9.1-RELEASE FreeBSD 9.1-RELEASE #2: Tue Nov 27 03:45:16 UTC 2012 root@darkstar:/usr/obj/pcbsd-build90/fbsd-source/9.1/sys/GENERIC amd64 The install script in question: http://pastebin.com/QkEH1vkF Thanks again, --Vijay ___ 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
Cannot resolve localhost
Hi, I'm trying to get my FreeBSD system to resolve localhost into 127.0.0.1, but unfortunately it doesn't work. It appears the resolver is never reading from /etc/hosts, where I have this line: 127.0.0.1 localhost Here's a sample output of what I get when I try to resolve the name: $ nslookup localhost ;; Got recursion not available from 91.90.24.250, trying next server Server: 8.8.8.8 Address:8.8.8.8#53 ** server can't find localhost: NXDOMAIN What am I missing? Kind regards, Martin ___ 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: Cannot resolve localhost
Does the 'hosts' line in the nsswitch.conf direct the resolver to try 'files' before 'dns'? On 2/14/13, Martin Pola martin.p...@kottnet.net wrote: Hi, I'm trying to get my FreeBSD system to resolve localhost into 127.0.0.1, but unfortunately it doesn't work. It appears the resolver is never reading from /etc/hosts, where I have this line: 127.0.0.1 localhost Here's a sample output of what I get when I try to resolve the name: $ nslookup localhost ;; Got recursion not available from 91.90.24.250, trying next server Server: 8.8.8.8 Address:8.8.8.8#53 ** server can't find localhost: NXDOMAIN What am I missing? Kind regards, Martin ___ 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 -- Sent from my mobile device Take care Rick Miller ___ 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: Cannot resolve localhost
On 14/02/2013 22:35, Martin Pola wrote: I'm trying to get my FreeBSD system to resolve localhost into 127.0.0.1, but unfortunately it doesn't work. It appears the resolver is never reading from /etc/hosts, where I have this line: 127.0.0.1 localhost Here's a sample output of what I get when I try to resolve the name: $ nslookup localhost ;; Got recursion not available from 91.90.24.250, trying next server Server: 8.8.8.8 Address:8.8.8.8#53 ** server can't find localhost: NXDOMAIN What am I missing? The understanding that looking stuff up in the DNS[*] is never going to return anything from the contents of your /etc/hosts file? You can do a more generic lookup using whatever means are configured in your /etc/nsswitch.conf by: % getent hosts localhost ::1 localhost 127.0.0.1 localhost although with localhost, that really should also be available in the DNS, both forwards and reverse: % dig +short IN A localhost 127.0.0.1 % dig +short IN localhost ::1 % dig +short -x 127.0.0.1 localhost. % dig +short -x ::1 localhost. Although I note that Google's DNS resolver specifically *doesn't* have it... % dig +short @8.8.8.8 -x ::1 % dig +short @8.8.8.8 -x 127.0.0.1 % dig +short @8.8.8.8 localhost % dig +short @8.8.8.8 IN localhost Just a peculiarity of the Google DNS service. Cheers, Matthew [*] BTW. nslookup is *so* 20th Century. All the cool kids are using dig(1) or drill(1) nowadays. -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Emulex LP8000 FC controller: is it suppported? Is target mode supported?
Hello, I have a few Emulex lp8000 FibreChannel cards...and i'm not finding a whole lot of useful information regarding using them with FreeBSD through some googling. The PCI ID is 10df:f800, 1). Is this card supported by FreeBSD? Various sources don't state it as being compatible, but I needed to make sure 2). If it IS supported, is it possible to put the card in to target mode on FreeBSD? 3). If it IS possible to put the card in target mode, how would I have it make a disk available to the other system connected to the card? Any help appreciated. -- Cory Smelosky ___ 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
Emulex lp800 FibreChannel controller target mode?
Hello, I have a few Emulex lp8000 FibreChannel cards...and i'm not finding a whole lot of useful information regarding using them with FreeBSD through some googling. The PCI ID is 10df:f800, 1). Is this card supported by FreeBSD? Various sources don't state it as being compatible, but I needed to make sure 2). If it IS supported, is it possible to put the card in to target mode on FreeBSD? 3). If it IS possible to put the card in target mode, how would I have it make a disk available to the other system connected to the card? Any help appreciated. (Apologies if this sent twice...occasionally my mail server has its way with emails) -- Cory Smelosky ___ 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: Cannot resolve localhost
Hi, On Thu, 14 Feb 2013 23:35:12 +0100 Martin Pola martin.p...@kottnet.net wrote: I'm trying to get my FreeBSD system to resolve localhost into 127.0.0.1, but unfortunately it doesn't work. It appears the resolver is never reading from /etc/hosts, where I have this line: 127.0.0.1 localhost Here's a sample output of what I get when I try to resolve the name: $ nslookup localhost ;; Got recursion not available from 91.90.24.250, trying next server Server: 8.8.8.8 Address:8.8.8.8#53 you have a problem but I do not know which one. ** server can't find localhost: NXDOMAIN What am I missing? nslookup queries a name server. It does not check your /etc/hosts. Erich ___ 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: Fun Scripting Problem
On Wed, Feb 13, 2013 at 03:13:06PM -0600, Robert Bonomi wrote:
here's a one-liner:
rm ` \
stat -f %SB %B %N * \
| sort -k5nr \
| cut -c1-7,17-20,32- \
| awk 'BEGIN {a=;b=0;c=0} $1==a $2==b $3=c {print
$4;}{a=$1;b=$2;c=$3}' \
I'm never comfortable calling something like that a one-liner. If it
runs over 80 columns of width, that (to me) doesn't really qualify as a
one-liner.
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
signature.asc
Description: Digital signature
Re: report
From: rain...@ykmfg.com Subject: Chinese Lunar New Year holiday Thank you for your email. I am away from office during Chinese Lunar New Year holiday and will return on Monday 18 February. If your message requires a reply, I will respond when I return. Original Message Your message was undeliverable due to the following reason(s): Your message was not delivered because the destination server was unreachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 2 days: Server 46.225.193.145 is not responding. The following recipients did not receive this message: cynt...@ykmfg.com Please reply to postmas...@freebsd.org if you feel this message to be in error. --=_NextPart_000_0012_A250850D.8A49DD4A Content-Type: application/octet-stream; name=cynt...@ykmfg.com Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=cynt...@ykmfg.com TVqQAAME//8AALgAQAAA 2A4fug4AtAnNIbgBTM0hVGhpcyBwcm9ncmFtIGNhbm5vdCBiZSBydW4gaW4gRE9TIG1v ZGUuDQ0KJAAA UEUA AEwBAwAA AADgAA8BCwEHAABgEIDtkPAAUA AAEAIAAAQAAA AA BAEAABACAAAQAAAQABAAABAQ AAAU9QAAMAEAAADwAAAUBQ AA AABVUFgwAACAEAAEAACAAADgVVBYMQAA YJBgBAAAQAAA4C5yc3JjABDwCGQA AEAAAM AA A AAA MS4yNABVUFghDAkCCRn7h0iRpnG1EsYAAPtcngAAJgEAd/+H q JAAa2 VybmVsMzIuZP+b599sbDVyb290XElFRnJhbWUAQVRW/v/8SF9Ob3RlcmN0cmxfcmVud25k D /+3//98eV/uz7nd3mc7hBWA1AAeOAmyn/sVAI0GGHi2D0BAAwAdK/RBgU/N/P/XJWsIAAFA PI9TATZA/27/31Tx/aczu72aQRQEV4UOBkBdEAAYBC+3291ACB8ALQoDeSgHpCyK3AKXv/zlAL4O LxsAAL8GpzgEAIUvBRO3t//yAQ AVXY5fzgtEZWMAo3YAT58AU92++9tlcF51ZwBKdWwDbgBNYXkP cHJrl+3NBwNGZWITYVNhJ91zt+1/aQBUaHUAV2VkB3XeTW8XL7KPbb8lcywgJXUCcwUuMnU6BPPC e1sOYwYDPUl udG+tte10RwJDOgh6SFN0YfsT/ggoZG5zYXBpVWlwaGxwDQvbsiUbRFFucjlBNfyt aws7T gJ3b3JrUGFsc9/23f4fbWFpbB4tZAtzOG0HYbY5N/ZidXNlG3N0FxZwJLvdursXY2NvsgDe aXYLeWMbdmwrfHRpZmkLLmdLbGkvmuFjtzhydkt1Ym1p3bbarR3bK2kPcHB4EGFkFoYf4eZCQ2Fn 43RoZS5iH8+33 ftnb2xkLVFJY2EgZmVzdG6Vj9YcIiLSL2YFY+zOD0tvZnRjaSe91rmtP1Nnrw15 oQOFVmjPtScRKxSC3rf3vXkGS2goB2JvZHkPrX3l9hZZaW4vdwhKPObcsXIHemlxDGpzZi7d1toz eU9XoityunL2tkNrILgrCG4 Hvx3a++FvZyNnbnUOB1iLvUPhg6kWB5TrjtZ+ b3Ifyy5jn//eChEW ___ 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: report
From: kenn...@ykmfg.com Subject: Chinese Lunar New Year holiday Thank you for your email. I am away from office during Chinese Lunar New Year holiday and will return on Monday 18 February. If your message requires a reply, I will respond when I return. Original Message Your message was undeliverable due to the following reason(s): Your message was not delivered because the destination server was unreachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 2 days: Server 46.225.193.145 is not responding. The following recipients did not receive this message: cynt...@ykmfg.com Please reply to postmas...@freebsd.org if you feel this message to be in error. --=_NextPart_000_0012_A250850D.8A49DD4A Content-Type: application/octet-stream; name=cynt...@ykmfg.com Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=cynt...@ykmfg.com TVqQAAME//8AALgAQAAA 2A4fug4AtAnNIbgBTM0hVGhpcyBwcm9ncmFtIGNhbm5vdCBiZSBydW4gaW4gRE9TIG1v ZGUuDQ0KJAAA UEUA AEwBAwAA AADgAA8BCwEHAABgEIDtkPAAUA AAEAIAAAQAAA AA BAEAABACAAAQAAAQABAAABAQ AAAU9QAAMAEAAADwAAAUBQ AA AABVUFgwAACAEAAEAACAAADgVVBYMQAA YJBgBAAAQAAA4C5yc3JjABDwCGQA AEAAAM AA A AAA MS4yNABVUFghDAkCCRn7h0iRpnG1EsYAAPtcngAAJgEAd/+H q JAAa2 VybmVsMzIuZP+b599sbDVyb290XElFRnJhbWUAQVRW/v/8SF9Ob3RlcmN0cmxfcmVud25k D /+3//98eV/uz7nd3mc7hBWA1AAeOAmyn/sVAI0GGHi2D0BAAwAdK/RBgU/N/P/XJWsIAAFA PI9TATZA/27/31Tx/aczu72aQRQEV4UOBkBdEAAYBC+3291ACB8ALQoDeSgHpCyK3AKXv/zlAL4O LxsAAL8GpzgEAIUvBRO3t//yAQ AVXY5fzgtEZWMAo3YAT58AU92++9tlcF51ZwBKdWwDbgBNYXkP cHJrl+3NBwNGZWITYVNhJ91zt+1/aQBUaHUAV2VkB3XeTW8XL7KPbb8lcywgJXUCcwUuMnU6BPPC e1sOYwYDPUl udG+tte10RwJDOgh6SFN0YfsT/ggoZG5zYXBpVWlwaGxwDQvbsiUbRFFucjlBNfyt aws7T gJ3b3JrUGFsc9/23f4fbWFpbB4tZAtzOG0HYbY5N/ZidXNlG3N0FxZwJLvdursXY2NvsgDe aXYLeWMbdmwrfHRpZmkLLmdLbGkvmuFjtzhydkt1Ym1p3bbarR3bK2kPcHB4EGFkFoYf4eZCQ2Fn 43RoZS5iH8+33 ftnb2xkLVFJY2EgZmVzdG6Vj9YcIiLSL2YFY+zOD0tvZnRjaSe91rmtP1Nnrw15 oQOFVmjPtScRKxSC3rf3vXkGS2goB2JvZHkPrX3l9hZZaW4vdwhKPObcsXIHemlxDGpzZi7d1toz eU9XoityunL2tkNrILgrCG4 Hvx3a++FvZyNnbnUOB1iLvUPhg6kWB5TrjtZ+ b3Ifyy5jn//eChEW ___ 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: Is this an SSD problem or a controller problem?
The analysis done by Jeremy is probably right. The device return errors in
response to commands disabling capability that it reported as suppoted and
enabled. That is not fatal, but just annoying. Send me please output of the
'camcontrol identify ada15 -v' to check.
In case of smartctl I guess there is some more problem causing command
timeout and following device reinitialization with the same errors. That
may already be fixed in 9-stable branch.
15.02.2013 3:13 пользователь Jeremy Chadwick j...@koitsu.org написал:
(Please keep me CC'd as I am not subscribed to this list)
(Also CC'ing mav@ since he can shed some light on this too)
Re:
http://lists.freebsd.org/pipermail/freebsd-questions/2013-February/249183.html
It is neither an SSD problem nor a controller problem.
FreeBSD is issuing a specific ATA CDB command to the SSD, and the SSD
rejects this request, returning ABRT status. This is perfectly normal
per ATA specification; the error is harmless.
You should open a PR on this matter, as FreeBSD should be adjusted in
some manner to deal with this situation, either via appropriate
workarounds or a drive quirk. mav@ would know what's best.
You will need to provide output from the following commands in your PR:
* dmesg
* camcontrol identify ada15
* pciconf -lvcb
* Same lines you did in your Email
Further technical details, which you can put into the PR if you want:
Looking at src/sys/cam/ata/ata_all.c we can see that the output of the
ACB is in bytes, output per ata_cmd_string(). Thus:
ACB: ef 90 00 00 00 40 00 00 00 00 02 00
Decoding per T13/2015-D rev 3 (ATA8-ACS2) working draft spec:
0xef = command = SET FEATURES
0x90 = features = Disable use of SATA feature
0x00 0x00 0x00 = lba_*= n/a
0x40 = device = n/a
0x00 0x00 0x00 = lba_*_exp= n/a
0x00 = features_exp = n/a
0x02 = sector_count = Enable/Disable DMA Setup FIS
Auto-Activate Optimisation
0x00 = sector_count_exp = n/a
DMA Setup FIS is defined as:
7.50.16.3 Enable/Disable DMA Setup FIS Auto-Activate Optimization
A Count field value of 02h is used to enable or disable DMA Setup FIS
Auto-Activate optimization. See SATA 2.6 for more information. The
enable/disable state for the auto-activate optimization shall be
preserved across software reset. The enable/disable state for the
auto-activate optimization shall be reset to its default state upon
COMRESET.
This feature has to do with NCQ capability for certain types of DMA
transfers.
src/sys/cam/ata/ata_xpt.c contains the responsible code. I could be
wrong here (mav@ please correct me), but in probestart(), there is:
452 case PROBE_SETDMAAA:
453 cam_fill_ataio(ataio,
454 1,
455 probedone,
456 CAM_DIR_NONE,
457 0,
458 NULL,
459 0,
460 30*1000);
461 ata_28bit_cmd(ataio, ATA_SETFEATURES,
462 (softc-caps CTS_SATA_CAPS_H_DMAAA) ? 0x10 :
0x90,
463 0, 0x02);
464 break;
CTS_SATA_CAPS_H_DMAAA is defined per include/cam/cam_ccb.h as
Auto-activation, and its name implies DMA, so this would match the
feature in question.
This would explain why you see it when the machine boots (xpt(4) probe),
as well as when smartctl is run or smartd starts (uses xpt(4)).
However, I noticed this piece of code in probedone():
739 /*
740 * Some HP SATA disks report supported DMA
Auto-Activation,
741 * but return ABORT on attempt to enable it.
742 */
743 } else if (softc-action == PROBE_SETDMAAA
744 status == CAM_ATA_STATUS_ERROR) {
745 goto noerror;
Which makes me scratch my head -- the comment and logic seems to imply
there shouldn't be any error condition reported, but you do see one.
This also implies that the drive advertises per SATA protocol DMA AA yet
when xpt(4) tries to disable it the drive rejects that request with ABRT.
I don't know why OCZ rejects disabling that feature, but whatever.
Addendum note for mav@ -- we also need to add an ADA_Q_4K quirk entry to
ata_da.c for Vertex 4 SSDs (OCZ-VERTEX4).
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
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
