Project

General

Profile

Bug #28411

Unauthorized system reboot

Added by Jordan Boxer over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Nice to have
Assignee:
Benno Rice
Category:
OS
Target version:
Seen in:
Severity:
Reason for Closing:
Duplicate
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

System shut down in the middle of the night and got this message: System booted at Fri Feb 9 08:03:43 2018 was not shut down properly


Related issues

Is duplicate of FreeNAS - Bug #27514: Break potential recursion involving getnewvnode and zfs_rmnodeDone

History

#1 Updated by Jordan Boxer over 2 years ago

  • File debug-ashwood-20180209152641.txz added
  • Private changed from No to Yes

#2 Updated by Dru Lavigne over 2 years ago

  • Seen in changed from Unspecified to 11.1
  • Reason for Blocked set to Need additional information

Jordan: was the system in use at the time? The reboot occurred at the same time the nightly jobs start (3 am). Is this the first time the system rebooted? As in, does it do this every morning at that time?

#3 Updated by Jordan Boxer over 2 years ago

Dru Lavigne wrote:

Jordan: was the system in use at the time? The reboot occurred at the same time the nightly jobs start (3 am). Is this the first time the system rebooted? As in, does it do this every morning at that time?

No, it was 3am and didn't notice until I got in to work this morning. It's not set up to reboot on its own ever and when I came nobody had access to the files until the drives were decrypted.

Thanks,
Jordan

#4 Updated by Dru Lavigne over 2 years ago

  • Assignee changed from Release Council to Alexander Motin
  • Reason for Blocked deleted (Need additional information)

Alexander: do you see any likely culprits in the logs?

#5 Updated by Dru Lavigne over 2 years ago

  • Target version set to 11.2-RC2

#6 Updated by Alexander Motin over 2 years ago

  • Assignee changed from Alexander Motin to Benno Rice

The only available kernel dump looks like another case of vnode recycle stack overflow.

Benno, just a thought: haven't you looked how stack usage happens in that call chain? May be we could remove some local variable somewhere to make it not happen despite of some hopefully limited recursion?

#7 Updated by Benno Rice over 2 years ago

  • Is duplicate of Bug #27514: Break potential recursion involving getnewvnode and zfs_rmnode added

#8 Updated by Dru Lavigne over 2 years ago

  • File deleted (debug-ashwood-20180209152641.txz)

#9 Updated by Dru Lavigne over 2 years ago

  • Status changed from Not Started to Closed
  • Target version changed from 11.2-RC2 to N/A
  • Private changed from Yes to No
  • Reason for Closing set to Duplicate

Jordan: you will be able to see the other ticket once the dev is finished with the other user's debug.

Also available in: Atom PDF