From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Kyle Rose <krose+linux-kernel@krose.org>, linux-kernel@vger.kernel.org
Subject: Re: Large-file corruption. ReiserFS? VFS?
Date: Sat, 13 Sep 2003 08:50:48 +0200 [thread overview]
Message-ID: <20030913085048.A22707@bitwizard.nl> (raw)
In-Reply-To: <20030911150017.T18851@schatzie.adilger.int>
On Thu, Sep 11, 2003 at 03:00:17PM -0600, Andreas Dilger wrote:
> True, and O_LARGEFILE would have bit you at 2GB and not 4GB... If you are
> doing output redirected from the shell, then it can't be a seek issue
> either.
Nah! Some programs just "try to seek" and if it works, will.
dd if=/dev/zero count=200 | strace sox -t raw -r 44100 -s -w - -t wav - > /tmp/test
dd if=/dev/zero count=200 | sox -t raw -r 44100 -s -w - -t wav - | dd of=/tmp/test
sox: Length in output .wav header will be wrong since can't seek to fix it
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
**** "Linux is like a wigwam - no windows, no gates, apache inside!" ****
next prev parent reply other threads:[~2003-09-13 6:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 20:28 Large-file corruption. ReiserFS? VFS? 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 [this message]
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
[not found] <uGoz.5NC.7@gated-at.bofh.it>
2003-09-11 20:49 ` Pascal Schmidt
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=20030913085048.A22707@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--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 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.