Re: log_sysevent: type 19 is not implemented messages during boot
On Fri, Jun 17, 2011 at 5:28 PM, Olivier Smedts oliv...@gid0.org wrote: 2011/6/17 Rolf Nielsen listrea...@lazlarlyricon.com: 2011-06-17 16:29, Artem Belevich skrev: ... Are you sure that it's harmless? It appeared for me as an evidence of pool breakage. I had these messages when I ran any zpool command on broken pool. I do't havesingle one after pool is fixed. Here's my thread on freebsd-fs : http://lists.freebsd.org/pipermail/freebsd-fs/2011-June/011639.html Indeed. Same story here. Last week I've got my pool corrupted due to a bad memory stick. Then I've got tons of thse log_sysevent: type 19... messages. After re-importing the pool with -F the messages went away. So, from where I stand, those messages do seem to correlate with a problem and should not be hushed by default. On mine, it pops up at boot on the console if the cache device is inaccessible (usb key). No real problem on the pool, but an information with more meaning would be useful. On one of my test systems, I have a zpool consisting of 3 HDDs in external enclosures attached via eSATA ports. If the enclosures are not powered (i.e. the disks are off), and the system boots, then this message appears. Of course, the zpool isn't available then, not being available physically. OTOH, when the enclosures are on, and the system boots, this message doesn't show up, and the zpool is available and healthy alright. This message appeared since ZFSv28, and on this system and in this specific scenario, it is absolutely harmless. /Rolf Olivier Smedts _ -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: log_sysevent: type 19 is not implemented messages during boot
W dniu 2011-06-11 18:43, Sergey Kandaurov pisze: On 11 June 2011 20:01, Rolf Nielsenlistrea...@lazlarlyricon.com wrote: Hi all, After going from 8.2-RELEASE to 8-STABLE (to get ZFS v28), I get log_sysevent: type 19 is not implemented exactly 20 times during boot. What does that message mean? Need I worry about it? And even if it's harmless, it annoys me, so can I get rid of it, and if so, how? Hi. This warning indeed came with ZFS v28 recently merged to 8-STABLE. AFAIK it's rather harmless. It was silenced in current recently (see svn r222343), and the fix is expected to be merged to 8-STABLE soon. Are you sure that it's harmless? It appeared for me as an evidence of pool breakage. I had these messages when I ran any zpool command on broken pool. I do't havesingle one after pool is fixed. Here's my thread on freebsd-fs : http://lists.freebsd.org/pipermail/freebsd-fs/2011-June/011639.html -- Bartosz Stec ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: log_sysevent: type 19 is not implemented messages during boot
On Fri, Jun 17, 2011 at 6:06 AM, Bartosz Stec bartosz.s...@it4pro.pl wrote: W dniu 2011-06-11 18:43, Sergey Kandaurov pisze: On 11 June 2011 20:01, Rolf Nielsenlistrea...@lazlarlyricon.com wrote: Hi all, After going from 8.2-RELEASE to 8-STABLE (to get ZFS v28), I get log_sysevent: type 19 is not implemented exactly 20 times during boot. What does that message mean? Need I worry about it? And even if it's harmless, it annoys me, so can I get rid of it, and if so, how? Hi. This warning indeed came with ZFS v28 recently merged to 8-STABLE. AFAIK it's rather harmless. It was silenced in current recently (see svn r222343), and the fix is expected to be merged to 8-STABLE soon. Are you sure that it's harmless? It appeared for me as an evidence of pool breakage. I had these messages when I ran any zpool command on broken pool. I do't havesingle one after pool is fixed. Here's my thread on freebsd-fs : http://lists.freebsd.org/pipermail/freebsd-fs/2011-June/011639.html Indeed. Same story here. Last week I've got my pool corrupted due to a bad memory stick. Then I've got tons of thse log_sysevent: type 19... messages. After re-importing the pool with -F the messages went away. So, from where I stand, those messages do seem to correlate with a problem and should not be hushed by default. Instead, they should probably be converted to something easier to understand by humans. Something like Oops. I do hope you had a backup of this pool. should do the trick. --Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: log_sysevent: type 19 is not implemented messages during boot
2011-06-17 16:29, Artem Belevich skrev: ... Are you sure that it's harmless? It appeared for me as an evidence of pool breakage. I had these messages when I ran any zpool command on broken pool. I do't havesingle one after pool is fixed. Here's my thread on freebsd-fs : http://lists.freebsd.org/pipermail/freebsd-fs/2011-June/011639.html Indeed. Same story here. Last week I've got my pool corrupted due to a bad memory stick. Then I've got tons of thse log_sysevent: type 19... messages. After re-importing the pool with -F the messages went away. So, from where I stand, those messages do seem to correlate with a problem and should not be hushed by default. Instead, they should probably be converted to something easier to understand by humans. Something like Oops. I do hope you had a backup of this pool. should do the trick. --Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I haven't had any problems at all. In the daily script I get all pools are healthy, and I have, AFAIK, experienced no data loss (and yes, I do daily backups). Seems to me it's a useless message, if it sometimes, but not always, signals a problem. /Rolf ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: log_sysevent: type 19 is not implemented messages during boot
2011/6/17 Rolf Nielsen listrea...@lazlarlyricon.com: 2011-06-17 16:29, Artem Belevich skrev: ... Are you sure that it's harmless? It appeared for me as an evidence of pool breakage. I had these messages when I ran any zpool command on broken pool. I do't havesingle one after pool is fixed. Here's my thread on freebsd-fs : http://lists.freebsd.org/pipermail/freebsd-fs/2011-June/011639.html Indeed. Same story here. Last week I've got my pool corrupted due to a bad memory stick. Then I've got tons of thse log_sysevent: type 19... messages. After re-importing the pool with -F the messages went away. So, from where I stand, those messages do seem to correlate with a problem and should not be hushed by default. Instead, they should probably be converted to something easier to understand by humans. Something like Oops. I do hope you had a backup of this pool. should do the trick. --Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I haven't had any problems at all. In the daily script I get all pools are healthy, and I have, AFAIK, experienced no data loss (and yes, I do daily backups). Seems to me it's a useless message, if it sometimes, but not always, signals a problem. On mine, it pops up at boot on the console if the cache device is inaccessible (usb key). No real problem on the pool, but an information with more meaning would be useful. /Rolf ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
log_sysevent: type 19 is not implemented messages during boot
Hi all, After going from 8.2-RELEASE to 8-STABLE (to get ZFS v28), I get log_sysevent: type 19 is not implemented exactly 20 times during boot. What does that message mean? Need I worry about it? And even if it's harmless, it annoys me, so can I get rid of it, and if so, how? TIA, Rolf Nielsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: log_sysevent: type 19 is not implemented messages during boot
On 11 June 2011 20:01, Rolf Nielsen listrea...@lazlarlyricon.com wrote: Hi all, After going from 8.2-RELEASE to 8-STABLE (to get ZFS v28), I get log_sysevent: type 19 is not implemented exactly 20 times during boot. What does that message mean? Need I worry about it? And even if it's harmless, it annoys me, so can I get rid of it, and if so, how? Hi. This warning indeed came with ZFS v28 recently merged to 8-STABLE. AFAIK it's rather harmless. It was silenced in current recently (see svn r222343), and the fix is expected to be merged to 8-STABLE soon. -- wbr, pluknet ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: log_sysevent: type 19 is not implemented messages during boot
2011-06-11 18:43, Sergey Kandaurov skrev: On 11 June 2011 20:01, Rolf Nielsenlistrea...@lazlarlyricon.com wrote: Hi all, After going from 8.2-RELEASE to 8-STABLE (to get ZFS v28), I get log_sysevent: type 19 is not implemented exactly 20 times during boot. What does that message mean? Need I worry about it? And even if it's harmless, it annoys me, so can I get rid of it, and if so, how? Hi. This warning indeed came with ZFS v28 recently merged to 8-STABLE. AFAIK it's rather harmless. It was silenced in current recently (see svn r222343), and the fix is expected to be merged to 8-STABLE soon. Ok. Thanks. :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
