From: Christian K <christian.andi@aon.at>
To: reiserfs-list@namesys.com
Subject: bug report: reiser4 kernel oops
Date: Fri, 26 May 2006 01:57:57 +0200 [thread overview]
Message-ID: <44764485.1060707@aon.at> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1576 bytes --]
Hello reiser4 team!
First, thanks for this great file system, i use it for all my files and
its really fast!
There is only a little problem using sparse files. When you create a big
sparse file on an reiser4 filesystem (parse file size must be greater
than filesystem size), create an filesystem at this sparse file (doesn't
matter which filesystem), mount the virtual filesystem and copy some
files to it, linux drops an reiser4 kernel oops and hangs when diskspace
is exhausted on the reiser4 filesystem(some sysreq keys keep functional)
I created a small script for reconstructing the problem on your own
system, be aware the system will possibly stop to work using it!
r4script expects 4 parameters:
1: partition where you would like to create the reiser4 filesystem (for
example /dev/sda2)
2: mount directory for reiser4 filesystem (for example /mnt/sda2),
3: mount directory of new reiserfs filesystem (for example /mnt/test)
4: directory containing files which should be copied to new filesystem ,
whole filesize (including all subdirectory files) should be greater than
reiser4 filesystem size. (for example /home)
If we use for example a sparse file on reiserfs filesystem the copy
process aborts only with the error "cp: cannot create regular file
`FILENAME': No space left on device"
Attachment zip contains necessary script files and screen photo showing
kernel oops message and register states.
Hope I could help you, feel free to contact me if you have any questions
or a solution for this problem!
Best regards
Christian
[-- Attachment #1.2: bugreport.zip --]
[-- Type: application/x-zip-compressed, Size: 93174 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
reply other threads:[~2006-05-25 23:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44764485.1060707@aon.at \
--to=christian.andi@aon.at \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.