All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaoli Feng <xifeng@redhat.com>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	samba-technical <samba-technical@lists.samba.org>
Subject: Re: fallocate can't change the cifs disk space usage
Date: Mon, 3 Aug 2020 04:46:12 -0400 (EDT)	[thread overview]
Message-ID: <342612495.44824091.1596444372983.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAH2r5muWV2P75oHToSR4_LaVWETXC1Y0LbpEWfD-rF00jfFMFg@mail.gmail.com>

Hell Steve,


----- Original Message -----
> From: "Steve French" <smfrench@gmail.com>
> To: "Xiaoli Feng" <xifeng@redhat.com>
> Cc: "CIFS" <linux-cifs@vger.kernel.org>, "samba-technical" <samba-technical@lists.samba.org>
> Sent: Monday, August 3, 2020 12:42:32 PM
> Subject: Re: fallocate can't change the cifs disk space usage
> 
> Any luck trying the same thing to Windows and/or Azure to see if this
> is possible Samba bug - sounds like possible Samba server bug but need
> more information.

Thanks for quick response. When trying the same thing to windows. This issue is gone.
fallocate can update the space usage.

> 
> Are you using one of the Samba plug in VFS modules on the server (like
> vfs_btrfs)?

I'm not using any samba plug in vfs.
 
> 
> What does the filesystem show (before and after) on the server side
> (local file system not just the remote view that Samba is returning
> for statfs) when you try the df -h?

on the server side, the space usage reported by df also keep the same before and
after fallocate.

> 
> On Sun, Aug 2, 2020 at 9:55 PM Xiaoli Feng <xifeng@redhat.com> wrote:
> >
> > Hello all,
> >
> > Recently when I'm investigating the xfstests generic/213 generic/228
> > failures for cifs.
> > Found that fallocate can't change the cifs disk space usage. Comparing xfs
> > fileystem,
> > fallocate can update space usage.
> >
> > My tests is in 5.8.0-rc7+. I also file a bug for this issue.
> >   https://bugzilla.kernel.org/show_bug.cgi?id=208775
> >
> > # cat /etc/samba/smb.conf
> > [cifs]
> > path=/mnt/cifs
> > writeable=yes
> > # mount //localhost/cifs cifs -o
> > user=root,password=redhat,cache=none,actimeo=0
> > # df -h cifs
> > Filesystem        Size  Used Avail Use% Mounted on
> > //localhost/cifs   36G   23G   13G  66% /root/cifs
> > #  fallocate -o 0 -l 2g /root/cifs/file1
> > # df -h cifs
> > Filesystem        Size  Used Avail Use% Mounted on
> > //localhost/cifs   36G   23G   13G  66% /root/cifs
> > ]# ls -l cifs
> > total 1
> > -rwxr-xr-x. 1 root root 2147483648 Aug  2 21:57 file1
> >
> > Thanks.
> >
> > --
> > Best regards!
> > XiaoLi Feng 冯小丽
> >
> 
> 
> --
> Thanks,
> 
> Steve
> 
> 


  reply	other threads:[~2020-08-03  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1119714633.44793917.1596421202774.JavaMail.zimbra@redhat.com>
2020-08-03  2:48 ` fallocate can't change the cifs disk space usage Xiaoli Feng
2020-08-03  4:42   ` Steve French
2020-08-03  8:46     ` Xiaoli Feng [this message]
2020-08-03 15:59   ` Steve French
2020-08-03 18:36     ` Steve French
2020-08-04 17:39   ` Steve French
2020-08-06  2:35     ` Xiaoli Feng

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=342612495.44824091.1596444372983.JavaMail.zimbra@redhat.com \
    --to=xifeng@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=smfrench@gmail.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.