|
|
Subject: Re: file attributes destroyed. - msg#00124
List: file-systems.reiserfs.general
On 26.10.2003 13:50, Vitaly Fertman wrote:
VF> would you take the latest reiserfsprogs from our ftp site (3.6.11) and run
VF> reiserfsck to be sure that there are no fs corruptions.
VF>
I now did. Actually I downloaded the latest Knoppix which contains reiserfsck
3.6.11.
Result: Nothing found.
I guess I'll just wait and see if it happens again.
Thank you very much for your help anyway.
reiserfsck --check started at Mon Oct 27 05:27:28 2003
###########
Replaying journal..
0 transactions replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 132833
Internal nodes 893
Directories 30379
Other files 461546
Data block pointers 17680796 (932 of them are zero)
Safe links 0
###########
reiserfsck finished at Mon Oct 27 05:44:58 2003
###########
--
Wolfgang
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
ReiserFS v3 + millions of files?
Greetings...
Long time ReiserFS user, first time I've had a problem. Signed up for the
mailing list last week, and was surprised to see so little traffic (might be
a good thing?).
I'm running Red Hat 7.3 using a Red Hat 2.4.20 kernel. The system has a
RAID-5 array via 3Ware 7500 controller, and three Western Digital 120GB
"Special Edition" hard drives. The array is one filesystem, ReiserFS. The
operating system, swap, and other files are stored on a hard drive that is on
the primary IDE controller off of the motherboard.
The system is a single board computer, with a P4 3.06 GHz hyperthreaded
processor (kernel is SMP enabled), 512MB of RAM, and contains a mix of
ReiserFS and EXT2 filesystems on the primary drive (ReiserFS only on the
array). No NFS.
The array is used to store what will basically amount to more than one million
files with an average size of sixty kilobytes.
During simulations for file writes, I'm seeing write performance begin to drop
dramatically after 800,000 files have been stored on the filesystem.
The filesystem is being mounted with the following options:
defaults,notail,noatime,nodiratime
The filesystem was created with default options, basically a "mkreiserfs /dev/
sda1".
Is this behavior I should expect from ReiserFS v3?
This week I will be switching from a Red Hat kernel to a vanilla kernel (from
kernel.org), first the latest 2.4 kernel, then the latest 2.6 kernel. After
that... I dunno.
Help?
--Dan Oglesby
Next Message by Date:
click to view message preview
Re: ReiserFS v3 + millions of files?
Dan Oglesby wrote:
Greetings...
Long time ReiserFS user, first time I've had a problem. Signed up for the
mailing list last week, and was surprised to see so little traffic (might be
a good thing?).
I'm running Red Hat 7.3 using a Red Hat 2.4.20 kernel. The system has a
RAID-5 array via 3Ware 7500 controller, and three Western Digital 120GB
"Special Edition" hard drives. The array is one filesystem, ReiserFS. The
operating system, swap, and other files are stored on a hard drive that is on
the primary IDE controller off of the motherboard.
The system is a single board computer, with a P4 3.06 GHz hyperthreaded
processor (kernel is SMP enabled), 512MB of RAM, and contains a mix of
ReiserFS and EXT2 filesystems on the primary drive (ReiserFS only on the
array). No NFS.
The array is used to store what will basically amount to more than one million
files with an average size of sixty kilobytes.
During simulations for file writes, I'm seeing write performance begin to drop
dramatically after 800,000 files have been stored on the filesystem.
The filesystem is being mounted with the following options:
defaults,notail,noatime,nodiratime
The filesystem was created with default options, basically a "mkreiserfs /dev/
sda1".
Is this behavior I should expect from ReiserFS v3?
This week I will be switching from a Red Hat kernel to a vanilla kernel (from
kernel.org), first the latest 2.4 kernel, then the latest 2.6 kernel. After
that... I dunno.
Help?
--Dan Oglesby
what size directories?
--
Hans
Previous Message by Thread:
click to view message preview
Re: file attributes destroyed.
On 26.10.2003 17:29, Hans Reiser wrote:
HR> Ah, wait, I forgot, did you ever use a kernel version older than 2.4.22
HR> on this fs? Could the corruption be from that time?
I am not sure how old this file system is but it has certainly seen 2.4.20
and 2.4.21.
However the files were still intact when I made my nightly backup last night.
I'll try reiserfsck later.
--
Wolfgang
Next Message by Thread:
click to view message preview
ReiserFS v3 + millions of files?
Greetings...
Long time ReiserFS user, first time I've had a problem. Signed up for the
mailing list last week, and was surprised to see so little traffic (might be
a good thing?).
I'm running Red Hat 7.3 using a Red Hat 2.4.20 kernel. The system has a
RAID-5 array via 3Ware 7500 controller, and three Western Digital 120GB
"Special Edition" hard drives. The array is one filesystem, ReiserFS. The
operating system, swap, and other files are stored on a hard drive that is on
the primary IDE controller off of the motherboard.
The system is a single board computer, with a P4 3.06 GHz hyperthreaded
processor (kernel is SMP enabled), 512MB of RAM, and contains a mix of
ReiserFS and EXT2 filesystems on the primary drive (ReiserFS only on the
array). No NFS.
The array is used to store what will basically amount to more than one million
files with an average size of sixty kilobytes.
During simulations for file writes, I'm seeing write performance begin to drop
dramatically after 800,000 files have been stored on the filesystem.
The filesystem is being mounted with the following options:
defaults,notail,noatime,nodiratime
The filesystem was created with default options, basically a "mkreiserfs /dev/
sda1".
Is this behavior I should expect from ReiserFS v3?
This week I will be switching from a Red Hat kernel to a vanilla kernel (from
kernel.org), first the latest 2.4 kernel, then the latest 2.6 kernel. After
that... I dunno.
Help?
--Dan Oglesby
|
|