archive mirror
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <>
To: <>, <>
Cc: LKML <>
Subject: Re: 2.5.75 does not boot - TCQ oops
Date: Sat, 12 Jul 2003 03:51:07 -0400	[thread overview]
Message-ID: <> (raw)

> [ Voluspa wrote: ]
> I took home 2.5.75-bk1, applied the tcq patch and then used the computer
> for five hours in the TCQ+TASKFILE environment. Filesystem is ext2. 
> No hickups. Except...

What would be the best approach to track down the problem?
I've recovered 99% of my system.
(rpm -V is a wonderful thing together with wget).

I intend to convert my root filesystem from reiserfs to xfs tomorrow
for the purposes of testing (and because I've had too many problems with 
reiser over time). Should I do this, and re-test TCQ to avoid any reiser 
problems, or should I stick with the current setup and do more testing as 
needed. I'll have to figure out some precautions if so :)
How can I help? 

On the good side, fs corruption dug out 10 gigs of free space
I never would have thought were available....cleanup for free.

             reply	other threads:[~2003-07-12  9:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12  7:51 Ivan Gyurdiev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-12 10:46 2.5.75 does not boot - TCQ oops Ivan Gyurdiev
2003-07-12 13:07 ` Voluspa
2003-07-12  4:05 Voluspa
2003-07-11  8:35 Voluspa
2003-07-11  2:51 Ivan Gyurdiev
2003-07-11  8:03 ` Jens Axboe
2003-07-11  8:28   ` Jens Axboe
2003-07-11  8:34     ` Jens Axboe
2003-07-11 10:54       ` Bartlomiej Zolnierkiewicz
2003-07-11 10:55         ` Jens Axboe
2003-07-11 20:58       ` Ivan Gyurdiev

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).