From: James M <dart@windeath.2y.net>
To: linux-kernel@vger.kernel.org, twaugh@redhat.com, wollny@cns.mpg.de
Subject: Parport/IMM/Zip Oops Revisited -- Filesys problem? Viro please look
Date: Tue, 14 Nov 2000 16:48:03 -0600 [thread overview]
Message-ID: <3A11C123.84DE0A95@windeath.2y.net> (raw)
In-Reply-To: <3A088352.BCAD0B7A@windeath.2y.net> <3A106A88.571AFF9E@windeath.2y.net>
James M wrote:
Was just trying to find out why I can mount in 11pre1 and 11pre2 when
Gert can't mount at all, so I removed my VFAT factory formatted zipdisk
and put in an Ext2 formatted one.....**BOOM**
Al, my original oops report is here:
http://boudicca.tux.org/hypermail/linux-kernel/2000week42/1240.html
Summary: Test10 is broken for both filesystems (sick of fsck'n-not
confirmed)
11pre1-pre2 work for VFAT broken for EXT2
11pre3 is broken for both filesystems
Anything you want me to try just let me know, I've already been
through about 100 fscks, a few more won't hurt.
BTW I have a list of 23 common non-obvious files that changed in
test10/11pre1 and 11pre2/pre3, say the word and I'll mail the list.
James M.
--30 Gig of fsck sucks--
-
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 prev parent reply other threads:[~2000-11-14 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 22:33 Re:test11-pre1 - Parport/IMM/Zip Oops fixed James M
2000-11-13 22:26 ` Re:test11-pre1 Parport/IMM/Zip Oops fixed -- Are we in Florida? James M
2000-11-14 22:48 ` James M [this message]
2000-11-14 23:42 ` Parport/IMM/Zip Oops Revisited -- Filesys problem? Viro please look Gert Wollny
2000-11-15 0:00 ` Parport/IMM/Zip Oops Revisited -- Filesys problem? Viro pleaselook James M
2000-11-15 2:26 ` Parport/IMM/Zip Oops Revisited -- Winbond James M
2000-11-15 11:08 ` Gert Wollny
2000-11-16 11:21 ` Parport/IMM/Zip LOCKUP Oops Revisited [patch included] Gert Wollny
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=3A11C123.84DE0A95@windeath.2y.net \
--to=dart@windeath.2y.net \
--cc=linux-kernel@vger.kernel.org \
--cc=twaugh@redhat.com \
--cc=wollny@cns.mpg.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®