From: Andrew Morton <akpm@zip.com.au>
To: Igor Briski <igor.briski@iskon.hr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3fs corruption problem?
Date: Thu, 27 Dec 2001 11:34:17 -0800 [thread overview]
Message-ID: <3C2B77B9.6143EE1E@zip.com.au> (raw)
In-Reply-To: <20011227120659.O3081@tsunami.iskon.hr>
Igor Briski wrote:
>
> I've noticed several files missing in last few days and this
> also started happening:
>
> webmail1 [/space/cwmail/mail/n_z1/f6/jejka74_Pmail_Ixxx_Ixx/2] # ls -la
> total 32
> drwx--S--- 2 www-data www-data 4096 Nov 25 22:47 .
> drwx--S--- 5 www-data www-data 4096 Dec 26 14:48 ..
> -rw-r--r-- 1 www-data www-data 1011 Nov 25 22:47 index.dat
> -rw-r--r-- 1 www-data www-data 18446744069414584903 Nov 23 22:25 m_0.dat
There was a truncate problem which could allow this. It was fixed
in 2.4.17. Deleting the file and running fsck will clean it up.
Could you please fsck the filesystems, see what it says?
Also, please check the logs for any errors or warnings from the
filesystem and from RAID.
Thanks.
-
next prev parent reply other threads:[~2001-12-27 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 11:06 ext3fs corruption problem? Igor Briski
2001-12-27 19:34 ` Andrew Morton [this message]
2002-01-04 14:56 ` Igor Briski
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C2B77B9.6143EE1E@zip.com.au \
--to=akpm@zip.com.au \
--cc=igor.briski@iskon.hr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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