On Sat, 30 Sep 2000, Anton Altaparmakov wrote: > All those problems disappear as soon as you change BLOCK_SIZE to 512. And Have you actually tried that? Go ahead, just do full backup before the experiment... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- reading 1 hardsector size, not one block size Matt_Domsch
- Re: reading 1 hardsector size, not one block size Anton Altaparmakov
- Re: reading 1 hardsector size, not one block s... Andries Brouwer
- Re: reading 1 hardsector size, not one blo... Anton Altaparmakov
- Re: reading 1 hardsector size, not one block size Alan Cox
- Re: reading 1 hardsector size, not one block s... Andre Hedrick
- RE: reading 1 hardsector size, not one block size Matt_Domsch
- Re: reading 1 hardsector size, not one block s... Andries Brouwer
- Re: reading 1 hardsector size, not one blo... Anton Altaparmakov
- Re: reading 1 hardsector size, not one... Alexander Viro
- Re: reading 1 hardsector size, no... Anton Altaparmakov
- Re: reading 1 hardsector size, no... Jeff V. Merkey
- Re: reading 1 hardsector size... Theodore Y. Ts'o
- Re: reading 1 hardsector ... Jeff V. Merkey
- Re: reading 1 hardsector ... Andre Hedrick
- Re: reading 1 hardsector ... Theodore Y. Ts'o
- Re: reading 1 hardsector ... Andre Hedrick
- Re: reading 1 hardsector ... Alexander Viro
- Re: reading 1 hardsector ... Peter Samuelson
- Re: reading 1 hardsector ... Andre Hedrick