dmesg VFS error

dmesg VFS error

Post by Ed Warnke » Wed, 06 Jun 2001 04:00:35



Anybody know what causes the following error message?

VFS: Disk change detected on device ide1(22,0)

  ed.warnken.vcf
< 1K Download
 
 
 

dmesg VFS error

Post by Michael Heimin » Wed, 06 Jun 2001 04:24:02



> Anybody know what causes the following error message?

> VFS: Disk change detected on device ide1(22,0)

Looks for me, as if you had changed the cdrom in your
cdrom drive, so it's not a real error message...

Please don't attach any kind of "v-cards" to your posts.

Good luck

Michael Heiming

 
 
 

dmesg VFS error

Post by Eric » Wed, 06 Jun 2001 16:23:33


Quote:> > Anybody know what causes the following error message?

> > VFS: Disk change detected on device ide1(22,0)

> Looks for me, as if you had changed the cdrom in your
> cdrom drive, so it's not a real error message...

It also may occur on HDD's.
And you certainly didn't replace a platter there :-)

dmesg logs can get spammed with these messages.
You'd need to turn off the CD autodetect tool in the gnome
panel to prevent the logs getting filled with these messages.
(Or kill the responsible process manually ofcourse)

Quote:> Please don't attach any kind of "v-cards" to your posts.

agreed.

Eric

 
 
 

1. VFS error in dmesg with ext3 htree

Here is a message I keep getting in my dmesg
when I mount my ext3 filesystems with htree
activated on 2.5.45-bk.

VFS: brelse: Trying to free free buffer
buffer layer error at fs/buffer.c:1166
Pass this trace through ksymoops for reporting
Call Trace:
 [<c0155db6>] __brelse+0x36/0x40
 [<c0155fd7>] bh_lru_install+0xc7/0x100
 [<c0156075>] __find_get_block+0x65/0x70
 [<c01560af>] __getblk+0x2f/0x70
 [<c015611f>] __bread+0x2f/0x80
 [<c0194223>] ext3_get_inode_loc+0xf3/0x190
 [<c0194e61>] ext3_reserve_inode_write+0x31/0xe0
 [<c01927c5>] commit_write_fn+0x25/0x90
 [<c0194f3b>] ext3_mark_inode_dirty+0x2b/0x60
 [<c0192419>] walk_page_buffers+0x69/0x70
 [<c0192966>] ext3_commit_write+0x136/0x270
 [<c01927a0>] commit_write_fn+0x0/0x90
 [<c013c68d>] generic_file_write_nolock+0x34d/
0x9f0
 [<c044f0ca>] sys_recvfrom+0xda/0x120
 [<c011d1d3>] schedule+0x1a3/0x340
 [<c01449a3>] __get_free_pages+0x33/0x40
 [<c013cedc>] generic_file_writev+0x5c/0x80
 [<c0153325>] do_readv_writev+0x175/0x290
 [<c0152c10>] do_sync_write+0x0/0xc0
 [<c0153575>] sys_writev+0x95/0xa0
 [<c0109413>] syscall_call+0x7/0xb

Anybody know how to fix this?  Thanks.

Jordan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. RAID 5 under Solaris 2.51

3. dmesg reports VFS error???

4. Sound Card Problems

5. VFS spam in dmesg?

6. Possibly broken kernel patch on SunOS 5.6

7. VFS - dmesg

8. internet and kernel 2.1.121

9. dmesg error: "*Bad* PSYND=..."?

10. MASQ errors in dmesg output

11. Errors in dmesg

12. please help me decypher the errors in dmesg

13. dmesg error in Solaris