From owner-freebsd-geom@FreeBSD.ORG Fri Nov 19 16:05:23 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E43AB16A4CE for ; Fri, 19 Nov 2004 16:05:23 +0000 (GMT) Received: from mtiwmhc12.worldnet.att.net (mtiwmhc12.worldnet.att.net [204.127.131.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9208943D53 for ; Fri, 19 Nov 2004 16:05:23 +0000 (GMT) (envelope-from duanewinner@worldnet.att.net) Received: from [10.10.100.90] (unknown[216.113.237.29]) by worldnet.att.net (mtiwmhc12) with ESMTP id <2004111916051911200mi6oae> (Authid: duanewinner); Fri, 19 Nov 2004 16:05:23 +0000 Message-ID: <419E19BE.20007@att.net> Date: Fri, 19 Nov 2004 11:05:18 -0500 From: Duane Winner User-Agent: Mozilla Thunderbird 0.9 (X11/20041108) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: GEOM: create disk during runtime? (security run output) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 16:05:24 -0000 Hello, I'm hoping somebody on this list can shed some light on this. My boss sent me a copy of his daily cron security run output, which contained this: localhost.local kernel log messages: GEOM: create disk ad0 dp=0xc6b77d60 GEOM: create disk cd0 dp=0xc69a8600 We're all running FreeBSD 5.2.1-p12. I've seen the "GEOM: create disk" messages plenty of times on boot and in my dmesg's, but never really paid much attention to them, since I don't really understand how GEOM works or how to interpret these kinds of messages. But I don't recall ever seeing it in a security run cronjob. My first question is "why is this happening during a security run cronjob? If this system is already booted and running, why is GEOM creating disks?" My second question is "is this something bad? Is it a red flag?" The only reasonable (and non-threatening) answer I could come up with is maybe it's because the machine went into or came out of suspend mode near the time the cronjob ran. (APM) The bottom line is I don't really know anything about GEOM, and would like to know what this means so preventative action can be taken if necessary. Thanks for any info, Duane