The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test7: XFS fills files with 0-bytes after crash
Date: Thu, 16 Oct 2003 21:38:35 +0200	[thread overview]
Message-ID: <3F8EF3BB.6090602@trash.net> (raw)

I recently encountered a problem with XFS: while hacking on some network 
stuff
I crashed my box multiple times. Every time I saved a file directly 
before the crash
XFS filled the file with 0-bytes (I assume at recovery). The file size 
was unchanged.
Syncing and waiting a couple of seconds before crashing the box helped. 
To confirm
my network hacking didn't accidentally damage XFS data structures I 
created a
module which does nothing more than dereferencing a NULL pointer in softirq
context, the problem persisted.

ver_linux:

Gnu C                  3.3.2
Gnu make               3.80
util-linux             2.12
mount                  2.12
module-init-tools      0.9.15-pre2
e2fsprogs              1.35-WIP
xfsprogs               2.5.11
nfs-utils              1.0.5
Linux C Library        2.3.2
Dynamic linker (ldd)   2.3.2
Procps                 3.1.12
Net-tools              1.60
Console-tools          0.2.3
Sh-utils               5.0.91
Modules Loaded         sch_hfsc iptable_filter ipt_MARK iptable_mangle 
ip_tables cls_fw oprofile nfsd exportfs deflate zlib_deflate twofish 
serpent aes blowfish des sha256 sha1 md5 af_key 8250 serial_core nfs 
lockd sunrpc af_packet snd_pcm_oss snd_mixer_oss snd_ens1371 snd_rawmidi 
snd_seq_device snd_pcm snd_page_alloc snd_timer snd_ac97_codec snd 
soundcore 8139too mii rtc unix

xfsprogs 2.5.11-1 (debian)

If more specific information is required please tell me ..

Best regards,
Patrick



             reply	other threads:[~2003-10-16 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16 19:38 Patrick McHardy [this message]
2003-10-16 20:30 ` 2.6.0-test7: XFS fills files with 0-bytes after crash Patrick McHardy

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=3F8EF3BB.6090602@trash.net \
    --to=kaber@trash.net \
    --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