Project

General

Profile

Bug #25532

Fix smartd panic

Added by René Keller over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Expected
Assignee:
Alexander Motin
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

After updating from 9.10.2-U5 to 11.0-U2 the system stops with a panic on the db commandline.
Just before this I got the Error: no such table: services_s3
If I boot in single user environment on the new version and do a zpool list, the Storage Pool with all data (S01) is not in the listing. If I revert back to the old version (via boot environment), everything is working and the status of the pool mentioned is OK.

Associated revisions

Revision 105412b3 (diff)
Added by tijl over 3 years ago

Add a patch to zero-initialise a variable that is passed to the kernel where it could trigger assertions. PR: 178032 Submitted by: op@hardenedbsd.org Approved by: samm@os2.kiev.ua (maintainer) Sponsored by: opBSD (cherry picked from commit f33582ebb85301637af8fbc94ec2d89121dbaa22) Ticket: #25532

History

#1 Updated by René Keller over 3 years ago

  • File debug-nas-20170810223156.txz added

#2 Updated by Sean Fagan over 3 years ago

There are two issues here -- one is that the upgrade didn't seem to work properly (for William, but the most likely case is switching from nightlies to stable at some point), the other is that smartd caused the system to panic ("cam_periph_runccb: ccb=0xfffff80011127000, func_code=0x4, flags=0xffff8ee0", so over to Alexander I think).

#3 Updated by Dru Lavigne over 3 years ago

  • Assignee changed from Release Council to Alexander Motin

#4 Updated by Alexander Motin over 3 years ago

  • Status changed from Unscreened to Ready For Release
  • Priority changed from No priority to Expected
  • Target version set to 11.0-U3
  • Seen in changed from Unspecified to 11.0-U2

I feel dejavue about smart issue. I think we already fixed that, and the patch is in nightly, but for some reason not in stable. Merged.

#5 Updated by Dru Lavigne over 3 years ago

  • File deleted (debug-nas-20170810223156.txz)

#6 Updated by Dru Lavigne over 3 years ago

  • Private changed from Yes to No

#7 Updated by Dru Lavigne over 3 years ago

  • Subject changed from Panic after Update 9.10.2-U5 to 11.0-U2 to Fix smartd panic

#8 Updated by Vaibhav Chauhan over 3 years ago

  • Status changed from Ready For Release to 47
  • Assignee changed from Alexander Motin to Joe Maloney

#9 Updated by Joe Maloney over 3 years ago

  • Assignee changed from Joe Maloney to Bonnie Follweiler

#10 Updated by Bonnie Follweiler over 3 years ago

  • Status changed from 47 to Ready For Release
  • Assignee changed from Bonnie Follweiler to Vaibhav Chauhan
  • Needs QA changed from Yes to No
  • QA Status Test Passes added
  • QA Status deleted (Not Tested)

Test passes - Upgrade from FN 9.10.2-U5 to FreeNAS-11.0-INTERNAL2-U3 (164236f50) had no smartd panic

#11 Updated by Dru Lavigne over 3 years ago

  • Assignee changed from Vaibhav Chauhan to Alexander Motin

#12 Updated by Vaibhav Chauhan over 3 years ago

  • Status changed from Ready For Release to Resolved

Also available in: Atom PDF