mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pascal Schmidt <der.eremit@email.de>
To: Kyle Rose <krose+linux-kernel@krose.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Large-file corruption. ReiserFS? VFS?
Date: Thu, 11 Sep 2003 22:49:42 +0200	[thread overview]
Message-ID: <E19xYNq-0001Iu-00@neptune.local> (raw)
In-Reply-To: <uGoz.5NC.7@gated-at.bofh.it>

On Thu, 11 Sep 2003 22:40:11 +0200, you wrote in linux.kernel:

> However, just as the write completed, the beginning of the file became
> corrupted.  I considered a 4GB problem to be likely, and re-tested
> with fewer source files such that the result would be smaller than
> 4GB; lo and behold, no corruption.  The same result occurs whether
> mkisofs is given the -o flag, or output is redirected to a file from
> stdout using the shell's redirection facility, suggesting the problem
> is probably at the kernel level.

Could also be that your mkisofs is not compiled with large file
support.

-- 
Ciao,
Pascal

       reply	other threads:[~2003-09-11 20:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <uGoz.5NC.7@gated-at.bofh.it>
2003-09-11 20:49 ` Pascal Schmidt [this message]
2003-09-11 20:28 Kyle Rose
     [not found] ` <20030911144732.S18851@schatzie.adilger.int>
2003-09-11 20:56   ` Kyle Rose
2003-09-11 21:00     ` Andreas Dilger
2003-09-13  6:50       ` Rogier Wolff
2003-09-13  6:51       ` Rogier Wolff
2003-09-12  9:36 ` Matthias Schniedermeyer
2003-09-12 11:47   ` Kyle Rose
2003-09-12 15:39 ` Oleg Drokin
2003-09-12 17:59   ` Mike Fedyk
2003-09-12 18:40     ` Oleg Drokin
2003-09-12 20:54       ` Mike Fedyk
2003-09-12 21:05         ` Kyle Rose
2003-09-12 21:56           ` Mike Fedyk
2003-09-13  0:46             ` Hans Reiser
2003-09-13  7:00         ` Oleg Drokin
2003-09-14 12:13   ` Kyle Rose

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=E19xYNq-0001Iu-00@neptune.local \
    --to=der.eremit@email.de \
    --cc=krose+linux-kernel@krose.org \
    --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

all inboxes | Powered by JetHome®