From: Eric Sandeen <sandeen@redhat.com>
To: Daniel Taylor <Daniel.Taylor@wdc.com>
Cc: tytso@mit.edu, amir73il@gmail.com, linux-ext4@vger.kernel.org
Subject: Re: inconsistent file placement
Date: Tue, 06 Jul 2010 21:29:53 -0500 [thread overview]
Message-ID: <4C33E6A1.7090408@redhat.com> (raw)
In-Reply-To: <469D2D911E4BF043BFC8AD32E8E30F5B24AEDF@wdscexbe07.sc.wdc.com>
Daniel Taylor wrote:
>> -----Original Message-----
>> From: tytso@mit.edu [mailto:tytso@mit.edu]
...
>> Speaking of fallocate.... if this is a NAS box than the file is
>> probably written using CIFS, right? Are you using a modern version of
>> Samba?
>
> Currently, we're on 3.2.5 of smdb, but that's because the later versions
> work less well with ext3. We will be testing them with ext4 now that
> we see the other options it offers.
>
> Soon as I can get the fallocate utility cross-built, there are some
> experiments that I want to run, but those will take a couple of days.
>
> Thanks again for all of your help.
http://sandeen.fedorapeople.org/utilities/fallocate.c
should be a simple compilable utility, or if for some reason
you don't have it in your glibc, you can call the syscall directly
with:
http://sandeen.fedorapeople.org/utilities/fallocate-via-syscall.c
(you may need to define SYS_fallocate & massage appropriately
depending on the architecture)
The tool in util-linux-ng is similar, and I think started with
this code, but its a quick hack so look out for bugs ;)
-Eric
next prev parent reply other threads:[~2010-07-07 2:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 1:49 inconsistent file placement Daniel Taylor
2010-07-06 2:38 ` Eric Sandeen
2010-07-06 6:52 ` Amir G.
2010-07-06 18:55 ` tytso
2010-07-06 18:59 ` Eric Sandeen
2010-07-06 22:01 ` tytso
2010-07-06 22:15 ` Daniel Taylor
2010-07-06 23:14 ` tytso
2010-07-06 23:39 ` Eric Sandeen
2010-07-07 1:08 ` Daniel Taylor
2010-07-07 2:29 ` Eric Sandeen [this message]
2010-07-06 23:34 ` Eric Sandeen
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=4C33E6A1.7090408@redhat.com \
--to=sandeen@redhat.com \
--cc=Daniel.Taylor@wdc.com \
--cc=amir73il@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.