Project

General

Profile

Bug #24099

Filter out useless messages

Added by Christoph Lampl over 1 year ago. Updated 12 months ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
William Grzybowski
Category:
Middleware
Target version:
11.1-BETA1
Seen in:
9.10.2-U3
Sprint:
Severity:
New
Backlog Priority:
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

tl;dr: When creating a new volume using WebGUI, FreeNAS shows following messages in the console:

May 22 18:53:45 freenas savecore: error reading last dump header at offset 17179865088 in /dev/dumpdev: Invalid argument

GEOM_ELI: Device da0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware
GEOM_ELI: Device da2p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware
GEOM_ELI: Device da3p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware
GEOM_ELI: Device da4p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware
GEOM_ELI: Device da5p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware

Steps:
When I decide to create a new volume using the volume manager, e.g. a RAIDZ2 using all of the 6 disks HGST 6 TB 4kn which are installed in this server, the volume itself work properly, however FreeNAS console lists the error message above.
The same error happens when I decide to create a volume with one vdev consisting of 3 disks and expand this volume by adding another vdev conisting of 3 disks later!

I'm wondering if this offset error has something to do with 4kn drives?

I wiped all disks before usage. However, this does not affect the error messsage while creating a new volume. They appear each time!

Thanks!

History

#1 Updated by Christoph Lampl over 1 year ago

  • File debug-storageunit-20170522191356.txz added

#2 Updated by William Grzybowski over 1 year ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Nice to have
  • Target version set to 11.0-U1

You can ignore these messages, not relevant.

#3 Updated by Christoph Lampl over 1 year ago

@ William: Thanks!

Just for info:

In case I detach and delete the volume, following error messages appear:

May 22 19:18:29 freenas syslog-ng12641: I/O error occured while writing; fd='23', error='Input/output error (5)'
May 22 19:18:29 freenas syslog-ng12641: I/O error occured while writing; fd='22', error='Input/output error (5)'
May 22 19:18:30 freenas syslog-ng12641: I/O error occured while writing; fd='21', error'Input/output error (5)'
May 22 19:18:31 freenas savecore: /dev/dumpdev: No such file or direcotry
May 22 19:18:35 freenas savecore: /dev/dumpdev: No such file or direcotry

I'm running on build FreeNAS-9.10.2-U3 (e1497f269)
Platform Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz
Memory 32625MB

#4 Updated by William Grzybowski over 1 year ago

  • Seen in changed from Unspecified to 9.10.2-U3

#5 Updated by William Grzybowski over 1 year ago

  • Target version changed from 11.0-U1 to 11.1

#6 Updated by William Grzybowski about 1 year ago

  • Status changed from Screened to Ready For Release
  • Needs QA changed from Yes to No

Crash dumps have been reworked on middleware so this should have been resolved in 11.1.

204fef8f4 f87bdb8a among others

#7 Updated by Dru Lavigne about 1 year ago

  • File deleted (debug-storageunit-20170522191356.txz)

#8 Updated by Dru Lavigne about 1 year ago

  • Private changed from Yes to No

#9 Updated by Dru Lavigne about 1 year ago

  • Subject changed from error reading last dump header at offset to Filter out useless messages

#10 Updated by Dru Lavigne about 1 year ago

  • Target version changed from 11.1 to 11.1-BETA1

#11 Updated by Dru Lavigne 12 months ago

  • Status changed from Ready For Release to Resolved

Also available in: Atom PDF