Re: logs rapidly fill /var partition
On Sat, 2004-01-24 at 09:54, Haines Brown wrote:
> When I run the command $ sudo rm -rf /mirror/partition, the activity
> is logged to /var/log/kern.log, syslog, and debug log.
>
> The problem is that each of these logs ends up 120 Mb in size and the
> remaining space in my 500 Mb /var partition quickly disappears.
>
> I need to know if this logging activity of this size is expected, and
> if so, what I might do about it. Increasing the partition size of /var
> partition I'd like to avoid. Because if the rm runs into trouble, I'm
> likey to know about it without the logs, and so a cron job run in
> parallel to periodically delete the logs is a possibility, but there
> must be a better way.
>
> Here's the beginning of debug where the rm command is issued. The rest
> of the log seems rather repititous
>
> ...
> Jan 24 04:57:41 teufel kernel: usb-storage: act_altsettting is 0
> Jan 24 04:57:41 teufel kernel: usb-storage: id_index calculated to be: 81
> Jan 24 04:57:41 teufel kernel: usb-storage: Array length appears to be: 83
> Jan 24 04:57:41 teufel kernel: usb-storage: USB Mass Storage device detected
> Jan 24 04:57:41 teufel kernel: usb-storage: Endpoints: In: 0xc42a2c34 Out: 0xc42a2c20 Int: 0xc42a2c48 (Period 32)
> Jan 24 04:57:41 teufel kernel: usb-storage: Found existing GUID 0d493000200e000022127397
> Jan 24 04:57:41 teufel kernel: WARNING: USB Mass Storage data integrity not assured
> Jan 24 04:57:41 teufel kernel: USB Mass Storage device found at 5
> Jan 24 05:00:01 teufel kernel: usb-storage: queuecommand() called
> Jan 24 05:00:01 teufel kernel: usb-storage: *** thread awakened.
> Jan 24 05:00:01 teufel kernel: usb-storage: Command READ_10 (10 bytes)
> Jan 24 05:00:01 teufel kernel: usb-storage: 28 00 00 00 00 22 00 00 02 00 65 f7
> Jan 24 05:00:01 teufel kernel: usb-storage: Bulk command S 0x43425355 T 0x8a745c Trg 0 LUN 0 L 1024 F 128 CL 10
> Jan 24 05:00:01 teufel kernel: usb-storage: Bulk command transfer result=0
> Jan 24 05:00:01 teufel kernel: usb-storage: usb_stor_transfer_partial(): xfer 1024 bytes
> Jan 24 05:00:01 teufel kernel: usb-storage: usb_stor_bulk_msg() returned 0 xferred 1024/1024
> Jan 24 05:00:01 teufel kernel: usb-storage: usb_stor_transfer_partial(): transfer complete
> Jan 24 05:00:01 teufel kernel: usb-storage: Bulk data transfer result 0x0
> Jan 24 05:00:01 teufel kernel: usb-storage: Attempting to get CSW...
> Jan 24 05:00:01 teufel kernel: usb-storage: Bulk status result = 0
> Jan 24 05:00:01 teufel kernel: usb-storage: Bulk status Sig 0x53425355 T 0x8a745c R 0 Stat 0x0
> Jan 24 05:00:01 teufel kernel: usb-storage: scsi cmd done, result=0x0
> Jan 24 05:00:01 teufel kernel: usb-storage: *** thread sleeping.
> Jan 24 05:00:01 teufel kernel: usb-storage: queuecommand() called
> Jan 24 05:00:01 teufel kernel: usb-storage: *** thread awakened.
> ...
>
I'm guessing that you've got your kernel compiled with usb mass storage
verbose debug, and most likely, you'll see this kind of output any time
you access your usb mass storage device - not just when using rm. If you
recompile your kernel (or perhaps just the module), I'm guessing you see
these extra messages disappear from your logs.
hope that helps,
-davidc
Reply to: