These errors can also be seen when the volume security style of your root volume (default is vol0) is set to ntfs instead of unix.
Grtz, Tom
On 15 Mar 2012, at 23:27, Dan Finn wrote:
filer> options autosupport autosupport.cifs.verbose off autosupport.content complete (value might be overwritten in takeover) autosupport.doit DONT autosupport.enable on (value might be overwritten in takeover) option autosupport.from: can not be read, command terminated (code=0xffffffff) autosupport.from unknown (value might be overwritten in takeover) autosupport.local.nht_data.enable off (value might be overwritten in takeover) autosupport.local.performance_data.enable off (value might be overwritten in takeover) autosupport.mailhost mail-relay-server (value might be overwritten in takeover) autosupport.minimal.subject.id hostname (value might be overwritten in takeover) autosupport.nht_data.enable on (value might be overwritten in takeover) autosupport.noteto (value might be overwritten in takeover) autosupport.partner.to (value might be overwritten in takeover) autosupport.performance_data.doit DONT autosupport.performance_data.enable on (value might be overwritten in takeover) autosupport.periodic.tx_window 1h (value might be overwritten in takeover) autosupport.retry.count 15 (value might be overwritten in takeover) autosupport.retry.interval 4m (value might be overwritten in takeover) autosupport.support.enable on (value might be overwritten in takeover) autosupport.support.proxy (value might be overwritten in takeover) autosupport.support.to autosupport@netapp.commailto:autosupport@netapp.com (value might be overwritten in takeover) autosupport.support.transport https (value might be overwritten in takeover) autosupport.support.url support.netapp.com/asupprod/post/1.0/postAsuphttp://support.netapp.com/asupprod/post/1.0/postAsup (value might be overwritten in takeover) autosupport.throttle on (value might be overwritten in takeover) autosupport.to myemail@domain.commailto:myemail@domain.com (value might be overwritten in takeover)
________________________________ From: Chaim Rieger <chaim.rieger@gmail.commailto:chaim.rieger@gmail.com> To: Dan Finn <dan_j_finn@yahoo.commailto:dan_j_finn@yahoo.com>; "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Sent: Thursday, March 15, 2012 4:13 PM Subject: Re: Strange error when running autosupport.doit
Options autosupport please -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Dan Finn <dan_j_finn@yahoo.commailto:dan_j_finn@yahoo.com> wrote: I noticed that when I run an autosupport.doit I get the following error:
Thu Mar 15 15:39:16 MDT [na04: asup.general.file.create.failed:error]: AutoSupport file (/mroot/etc/log/.cm_stats_hourly_done) was unable to be written to the file spool subdirectory.
But the autosupport email still makes it out and looks good. I deleted everything under /etc/log/autosupport and I also tested that I could create the file that is mentioned in the error manually as root, no issues there.
Anyone else ever seen this before?
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters