Re: Linux 2.4 - 2.6 migration

2003-11-08 Thread Soeren Sonnenburg
On Fri, 2003-11-07 at 16:09, Jure Pear wrote:
 On Fri, 07 Nov 2003 14:39:06 +0100
 Sebastian Kaps [EMAIL PROTECTED] wrote:
 
  Another thing: I had to hard reboot my system a few times in the last
  few months. I also experienced that sometimes parts of files were
  overwritten with 0x00s or parts of other files. Can someone explain to
  me how this can happen?
 
 Sounds to me like you'd want to check your hardware and ram. I'm dual
 booting between redhat 2.4.20-something and 2.6.0-test9 and have no problems
 wih reiserfs partitions.

Nope that is expected behaviour without data logging patches.

Soeren



Re: Linux 2.4 - 2.6 migration

2003-11-08 Thread Alex Zarochentsev
On Fri, Nov 07, 2003 at 02:39:06PM +0100, Sebastian Kaps wrote:
 Hi!
 
 Is there something concerning ReiserFS I should know when migrating from
 Linux 2.4 to Linux 2.6?
 
 I'm asking because a few days ago I downloaded and compiled 2.6.0-test9
 just for curiosity. It booted fine and I went back to my standard
 kernel, which was 2.4.23-pre5 at that time. Right after booting the
 2.4.x kernel, I got lots of the following messages in my logs:
 ,
 | kernel: ide2(33,3):vs-4080: reiserfs_free_block: free_block 
 (2103:463529)[dev:blocknr]: bit already cleared

test-9/reiser3 works fine for us.  Your problems could be due to a bug in
updated IDE driver, for example.  Do other filesystems (like ext2) work? 

Can you send a .config (from 2.6.0-test-9) and describe your hardware configuration
to the [EMAIL PROTECTED] mailing list?

 `
 The block number always differed. Gladly, reiserfsck --rebuild-tree
 helped to cure that, but there were lots of unusable files after that
 (e.g. parts of files overwritten with parts of other files).

I think that reiserfsck --rebuild-tree trusts the bitmap content, which is not
good for your case.  Vitaly will answer better.

 
 Is this suppose to happen? What caused this error?
 
 Another thing: I had to hard reboot my system a few times in the last
 few months. I also experienced that sometimes parts of files were
 overwritten with 0x00s or parts of other files. Can someone explain to
 me how this can happen?
 
 -- 
 Ciao, Sebastian

-- 
Alex.


Re: Linux 2.4 - 2.6 migration

2003-11-08 Thread Vitaly Fertman
On Saturday 08 November 2003 13:11, Alex Zarochentsev wrote:
 On Fri, Nov 07, 2003 at 02:39:06PM +0100, Sebastian Kaps wrote:
  Hi!
 
  Is there something concerning ReiserFS I should know when migrating from
  Linux 2.4 to Linux 2.6?
 
  I'm asking because a few days ago I downloaded and compiled 2.6.0-test9
  just for curiosity. It booted fine and I went back to my standard
  kernel, which was 2.4.23-pre5 at that time. Right after booting the
  2.4.x kernel, I got lots of the following messages in my logs:
  ,
 
  | kernel: ide2(33,3):vs-4080: reiserfs_free_block: free_block
  | (2103:463529)[dev:blocknr]: bit already cleared

 test-9/reiser3 works fine for us.  Your problems could be due to a bug in
 updated IDE driver, for example.  Do other filesystems (like ext2) work?

 Can you send a .config (from 2.6.0-test-9) and describe your hardware
 configuration to the [EMAIL PROTECTED] mailing list?

  `
  The block number always differed. Gladly, reiserfsck --rebuild-tree
  helped to cure that, but there were lots of unusable files after that
  (e.g. parts of files overwritten with parts of other files).

 I think that reiserfsck --rebuild-tree trusts the bitmap content, which is
 not good for your case.  Vitaly will answer better.

Bitmaps do not say that this block belongs to some particular file,
so bitmaps have nothing to do with the described problem when 
parts of files overwritten with parts of other files. But when there
are some blocks in use that have been already freed there could 
be another problem -- parts of files are lost, there are just zeroes 
in these parts, or some files are lost after fsck. Probably scanning
through all blocks of the partition with --scan-whole-partition 
option would help here, but this option should be used with 
extreme caution as you can run out of the partition space with it.

-- 
Thanks,
Vitaly Fertman


Re: Linux 2.4 - 2.6 migration

2003-11-08 Thread Matthias Andree
Sebastian Kaps [EMAIL PROTECTED] writes:

 Is there something concerning ReiserFS I should know when migrating from
 Linux 2.4 to Linux 2.6?

No. Make sure the file system is fine before booting a new kernel, using
a CURRENT reiserfsprogs is essential. Namesys have made lots of fixes
recently.

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95


Re: Linux 2.4 - 2.6 migration

2003-11-08 Thread Sebastian Kaps
Hi Quinn!

 Did you enable IDE TCQ in your 2.6 kernel?  To quote http://www.namesys.com/
 download.html

I guess I did enable TCQ.

 Don't enable TCQ (Tagged Command Queuing) in 2.5 (and modified 2.4) kernels. 
 TCQ is known broken currently and it will corrupt your filesystems for sure.

Okay, that would explain it...

-- 
Ciao, Sebastian


Re: Linux 2.4 - 2.6 migration

2003-11-08 Thread Sebastian Kaps
Hi Alex!

 test-9/reiser3 works fine for us.  Your problems could be due to a bug in
 updated IDE driver, for example.  Do other filesystems (like ext2) work? 

I only have one big reiserfs partition, so I can't test it.

 Can you send a .config (from 2.6.0-test-9) and describe your hardware
 configuration to the [EMAIL PROTECTED] mailing list?

Sorry, I did an rm -rf on the 2.6.x tree two days ago. I guess that
enabling TCQ was the mistake, as Quinn Harris pointed out.

-- 
Ciao, Sebastian


Re: Linux 2.4 - 2.6 migration

2003-11-08 Thread Alejandro Sanchez Acosta
El s?, 08-11-2003 a las 05:08, Quinn Harris escribió:
 Did you enable IDE TCQ in your 2.6 kernel?  To quote http://www.namesys.com/
 download.html
 Don't enable TCQ (Tagged Command Queuing) in 2.5 (and modified 2.4) kernels. 
 TCQ is known broken currently and it will corrupt your filesystems for sure.

What does it do Tagged Command Queuing?

Thanks in advance.
-- 
Alejandro Sanchez Acosta [EMAIL PROTECTED]



Re: Linux 2.4 - 2.6 migration

2003-11-08 Thread Marcelo Pacheco
On Sunday 09 November 2003 03:45, Alejandro Sanchez Acosta wrote:
 El s?, 08-11-2003 a las 05:08, Quinn Harris escribió:
  Did you enable IDE TCQ in your 2.6 kernel?  To quote
  http://www.namesys.com/ download.html
  Don't enable TCQ (Tagged Command Queuing) in 2.5 (and modified 2.4)
  kernels. TCQ is known broken currently and it will corrupt your
  filesystems for sure.

 What does it do Tagged Command Queuing?

 Thanks in advance.
TCQ is a feature that allows a host to send multiple commands to IDE devices 
and have them queued and executed in the most efficient manner to the device, 
being interrupted as they become ready. This is a standard SCSI feature that 
is available on higher featured drives. Lots of drives don't have this 
feature, but once it's stable on Linux, it should be ok to enable it by 
default and let Linux disable it for devices that don't support it. However 
today it's not ready for production.

Marcelo Pacheco



Re: Linux 2.4 - 2.6 migration

2003-11-07 Thread Quinn Harris
Did you enable IDE TCQ in your 2.6 kernel?  To quote http://www.namesys.com/
download.html
Don't enable TCQ (Tagged Command Queuing) in 2.5 (and modified 2.4) kernels. 
TCQ is known broken currently and it will corrupt your filesystems for sure.

Quinn


On Friday 07 November 2003 06:39 am, Sebastian Kaps wrote:
 Hi!
 
 Is there something concerning ReiserFS I should know when migrating from
 Linux 2.4 to Linux 2.6?
 
 I'm asking because a few days ago I downloaded and compiled 2.6.0-test9
 just for curiosity. It booted fine and I went back to my standard
 kernel, which was 2.4.23-pre5 at that time. Right after booting the
 2.4.x kernel, I got lots of the following messages in my logs:
 ,

 | kernel: ide2(33,3):vs-4080: reiserfs_free_block: free_block
 | (2103:463529)[dev:blocknr]: bit already cleared

 `
 The block number always differed. Gladly, reiserfsck --rebuild-tree
 helped to cure that, but there were lots of unusable files after that
 (e.g. parts of files overwritten with parts of other files).
 
 Is this suppose to happen? What caused this error?
 
 Another thing: I had to hard reboot my system a few times in the last
 few months. I also experienced that sometimes parts of files were
 overwritten with 0x00s or parts of other files. Can someone explain to
 me how this can happen?
 
 -- 
 Ciao, Sebastian