errors.log full of "Assuming drive cache: write through"

Ask questions about Arch Linux ARM. Please search before making a new topic.

errors.log full of "Assuming drive cache: write through"

Postby silentcreek » Thu Feb 07, 2013 8:43 pm

Hi,

I got a Pogoplug v3 with 3 USB devices set up (sda is a flash drive for the alarm installation, sdb and sdc are USB hard drives used for my samba shares). If I take a look in /etc/errors.log I see dozens of lines with the same message for all of my USB devices - they all occur during times when the device boots up:
$this->bbcode_second_pass_code('', 'Feb 7 17:01:19 alarm kernel: [ 8.590000] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Feb 7 17:01:19 alarm kernel: [ 8.600000] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Feb 7 17:01:19 alarm kernel: [ 8.870000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
Feb 7 17:01:19 alarm kernel: [ 8.880000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
Feb 7 17:01:19 alarm kernel: [ 8.970000] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Feb 7 17:01:19 alarm kernel: [ 9.190000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
Feb 7 17:01:19 alarm kernel: [ 10.040000] sd 2:0:0:0: [sda] Assuming drive cache: write through
Feb 7 17:01:19 alarm kernel: [ 10.050000] sd 2:0:0:0: [sda] Assuming drive cache: write through
Feb 7 17:01:19 alarm kernel: [ 10.080000] sd 2:0:0:0: [sda] Assuming drive cache: write through')

I asked google, and as far as I understand, these messages occur since the USB drives don't have a write cache, hence these are not really errors.

However, is it possible to avoid these messages during boot up? Like, can I let my kernel know that these drives don't have a write cache so it won't look for it, or so? Or just supress thisoutput somehow?

Thanks,

Timo
silentcreek
 
Posts: 21
Joined: Mon Jan 07, 2013 8:38 pm

Return to User Questions

Who is online

Users browsing this forum: Google [Bot] and 13 guests