From: Vladislav Malyshkin <mal@gromco.com>
To: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: 2.2.16-22 (RedHat 7.0) fs problem
Date: Tue, 28 Nov 2000 15:21:44 -0500 [thread overview]
Message-ID: <3A2413D8.69C18FF8@gromco.com> (raw)
when doing mount/umount of a MSDOS floppy on 2.2.16-22
I often get
/var/log/messages.1:Nov 25 21:02:18 localhost kernel: set_blocksize: dev
02:00 buffer_dirty 19 size 512
/var/log/messages.2:Nov 16 18:19:05 localhost kernel: set_blocksize: dev
02:00 buffer_dirty 19 size 512
Is this harmless or sume bug in the filesystem?
Vladislav
The system is:
processor : 0
vendor_id : GenuineIntel
cpu family : 5
model : 2
model name : Pentium 75 - 200
stepping : 5
cpu MHz : 90.001
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : yes
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8
bogomips : 179.40
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-28 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 20:21 Vladislav Malyshkin [this message]
2000-11-28 20:38 ` 2.2.16-22 (RedHat 7.0) fs problem Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A2413D8.69C18FF8@gromco.com \
--to=mal@gromco.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.