1

File access after fsck very slow for first-time access?

view story
linux-howto

http://unix.stackexchange.com – My drive started to show up errors, I unmounted it and ran fsck on it. It's a 2TB drive installed on Debian Squeeze, using ext3. The fsck too about 17 hours. I found some, luckily mostly unimportant, files in lost+found. But when I tried to access anything on that FS, first time access (reading directory listing, reading file information, reading file data) is very slow and takes up to one or two seconds. Accessing anything a second time seems to be normal. Given that I've around 1.5TB data on it, that's a lot times for "first access after mount". However, I don't see anything in the logs (HowTos)

Danial's picture
Submitted by Danial on 01/13/2013

Stories similar to File access after fsck very slow for first-time access?

Is there any sense in running fsck -N first or should we just use -y right away and get it all over and done with fast?

When we run fsck or e2fsck with the -y option and there are some serious file system problems, it silently unlinks any orphaned files to the lost+found. That's all fine and dandy when there's no big problems, normally no files need to be unlinked and fsck just runs and fixes t

Possible Duplicate: How do you get e2fsck to show progress information?

Is there a way to check the progress of fsck.ext3 under Ubuntu, if I'm logged in remotely?

Obviously the time taken depends on a lot of factors, but if fsck has to option of displaying a progress bar, it should be possible

EDIT: Seems I didn't make the question clear enough.

I wrote a Java application that checks and indexes huge archive files. When i test it on my local machine, everything is speedy and works like a charm.

I have a server with MS Access installed, and Via Remote Data Connection, the response time is excellent. The database is 1.3 gb, and the queries use a series of ODBC links to acquire data throughout the network.

However, when I map the drive to a networked drive on the local PCs, response time is horrendous.

I installed sarg from sarg rpm and i am facing issue while generating sarg reports and getting this time different error below

sarg -l /var/log/squid/access.log SARG: Records in file: 242332, reading: 0.00% SARG: Records in file: 242332, reading: 2.06% SARG: Records in file: 242332, reading: 4.13% SARG: Records in file: 242332, reading: 6.19%

Hi,

After some difficulties accessing to my NAS network in writing mode (1 TO, bought one year ago), I launched a fsck -yvf; now gparted tells me it gots no partition ... I made a tesdisk /dev/sdb1> Proceed> Intel> Analyze> Quick search> Yes After several hours the partition was not found.

File system repaired? 40 weeks 16 hours ago

Hello,

yesterday I made a backup onto my external harddisk (ext3 formatted) via rsync. After some time it returned

Code: rsync: stat "/media/my_harddisk/some/dir/foo.bar" failed: Input/output error (5) rsync error: some files could not be transferred (...) I then unmounted the disk and started fsck to check it. fsck told me, that the file system seems to be corrupt.

I have a Debian box with additional ( it is not a system disk ) 1.5Tb sata hdd (wd caviar green). There is only one partition on the whole disk.

Disk is used for backups from remote system (with rsnapshot, backup update runs every 4 hours) and rtorrent for some files.