On Tue, 7 Apr 2015 08:10:28 +1000 Cameron Simpson wrote:
> On 06Apr2015 10:53, Gordon Messmer wrote:
> >On 04/01/2015 09:20 PM, Cameron Simpson wrote:
> >>>$ du -sh kmeans --apparent-size
> >>>154Gkmeans
> >>>
> >>>$ du -sh kmeans
> >>>628Gkmeans
> >>
> >>That looks backwards to me, pres
On 06Apr2015 10:53, Gordon Messmer wrote:
On 04/01/2015 09:20 PM, Cameron Simpson wrote:
$ du -sh kmeans --apparent-size
154Gkmeans
$ du -sh kmeans
628Gkmeans
That looks backwards to me, presuming you have sparse files?
It makes sense if there's a very large number of files of less
On 04/01/2015 09:20 PM, Cameron Simpson wrote:
$ du -sh kmeans --apparent-size
154Gkmeans
$ du -sh kmeans
628Gkmeans
That looks backwards to me, presuming you have sparse files?
It makes sense if there's a very large number of files of less than 2k
each, while Isilon OneFS uses an
On 02Apr2015 07:54, Ranjan Maitra wrote:
On Thu, 2 Apr 2015 15:20:52 +1100 Cameron Simpson wrote:
Yes, it is on the same directory of the remote Inselon FS mounted as a cifs
mount on a F21 system.
The same command on my local disk (F21 machine, ext4 FS) yields:
$ du -sh kmeans --apparent-siz
On Thu, 2 Apr 2015 15:20:52 +1100 Cameron Simpson wrote:
> On 01Apr2015 08:07, Ranjan Maitra wrote:
> >Thanks to both Cameron and you, Bob!
> >
> >After the transfer, here is what we have, on that filesystem:
> >
> >$ du -sh kmeans --apparent-size
> >154G kmeans
> >
> >$ du -sh kmeans
> >628G km
Deduplication kind of handles sparse files since all blocks containing only
zero will get mapped to the same storage.
As soon as one of those blocks sharing storage get written to it will be
written to a new block, and the usage counter of the shared block gets reduced
by one. Once usage reache
On 01Apr2015 08:07, Ranjan Maitra wrote:
Thanks to both Cameron and you, Bob!
After the transfer, here is what we have, on that filesystem:
$ du -sh kmeans --apparent-size
154Gkmeans
$ du -sh kmeans
628Gkmeans
That looks backwards to me, presuming you have sparse files?
Although "ma
On 04/01/2015 10:57 AM, Ranjan Maitra wrote:
Thanks!
That's EMC's "OneFS" filesystem (EMC bought out Isilon).
On Wed, 1 Apr 2015 08:07:34 -0500 Ranjan Maitra
wrote:
Thanks to both Cameron and you, Bob!
After the transfer, here is what we have, on that filesystem:
$ du -sh kmeans --appa
Thanks!
> That's EMC's "OneFS" filesystem (EMC bought out Isilon).
>
> > On Wed, 1 Apr 2015 08:07:34 -0500 Ranjan Maitra
> > wrote:
> >
> >> Thanks to both Cameron and you, Bob!
> >>
> >> After the transfer, here is what we have, on that filesystem:
> >>
> >> $ du -sh kmeans --apparent-size
>
On 04/01/2015 07:07 AM, Ranjan Maitra wrote:
Btw, I just found out that the filesystem in question is an Isilon filesystem.
That's EMC's "OneFS" filesystem (EMC bought out Isilon).
On Wed, 1 Apr 2015 08:07:34 -0500 Ranjan Maitra
wrote:
Thanks to both Cameron and you, Bob!
After the trans
Btw, I just found out that the filesystem in question is an Isilon filesystem.
Ranjan
On Wed, 1 Apr 2015 08:07:34 -0500 Ranjan Maitra
wrote:
> Thanks to both Cameron and you, Bob!
>
> After the transfer, here is what we have, on that filesystem:
>
> $ du -sh kmeans --apparent-size
> 154G k
Thanks to both Cameron and you, Bob!
After the transfer, here is what we have, on that filesystem:
$ du -sh kmeans --apparent-size
154Gkmeans
$ du -sh kmeans
628Gkmeans
So, I guess that leaves me (and others) stuck.
Ranjan
On Mon, 30 Mar 2015 21:14:38 -0500 Robert Nichols
wrote:
>
On 03/30/2015 04:39 PM, Ranjan Maitra wrote:
Thanks, Cameron!
If the far end is windows, certainly sparse files will no longer be sparse at
the far end. This kind of thing is one reason we get so picky when getting
employers to order NASes; we asked for a QNAP (cheap, useful, Linux backend)
and
On 30Mar2015 16:39, Ranjan Maitra wrote:
Thanks, Cameron!
Any time.
If you are using a CIFS share, does that mean the far end is not a UNIX
filesystem? The -S (sparse) option is only useful if the backend can store
sparse files, otherwise the backend will just store lots of blocks of zeroes
Thanks, Cameron!
> If you are using a CIFS share, does that mean the far end is not a UNIX
> filesystem? The -S (sparse) option is only useful if the backend can store
> sparse files, otherwise the backend will just store lots of blocks of zeroes
> (presuming you really have sparse files).
T
On 30Mar2015 11:29, Ranjan Maitra wrote:
I am at my wits end with this, so I thought I would post here to see if anyone
had any thoughts. The only connection with F21 (updated in all installed
components) is that everything is on a F21 machine.
So, I have a cifs share mounted onto /mnt/space
Sorry I forgot to add that there are no symlinks in the directories being
rsync'ed so that is not an issue here.
Best wishes,
Ranjan
On Mon, 30 Mar 2015 11:29:07 -0500 Ranjan Maitra
wrote:
> Hi,
>
> I am at my wits end with this, so I thought I would post here to see if
> anyone had any tho
Hi,
I am at my wits end with this, so I thought I would post here to see if anyone
had any thoughts. The only connection with F21 (updated in all installed
components) is that everything is on a F21 machine.
So, I have a cifs share mounted onto /mnt/space using the usual mount.cifs
option with
18 matches
Mail list logo
