Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Andreas Schneider <asn@cryptomilk.org>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org, samba-technical@lists.samba.org
Subject: Re: btrfs and default directory link count
Date: Fri, 08 Nov 2013 15:11:41 +0100	[thread overview]
Message-ID: <13844973.BJjIDpTNz7@magrathea> (raw)
In-Reply-To: <CAE5mzvgtAryNUTkSQY0_cLyVPOHzig5Jw9ghL_Kd-b-vPbAxTw@mail.gmail.com>

On Friday 08 November 2013 06:24:01 cwillu wrote:
> On Fri, Nov 8, 2013 at 5:07 AM, Andreas Schneider <asn@cryptomilk.org> 
wrote:
> > Hello,
> > 
> > I did run the Samba testsuite and have a failing test
> > (samba.vfstest.stream_depot). It revealed that it only fails on btrfs. The
> > reason is that a simple check fails:
> > 
> > if (smb_fname_base->st.st_ex_nlink == 2)
> > 
> > If you create a directory on btrfs and check stat:
> > 
> > $ mkdir x
> > $ stat x
> > 
> >   File: ‘x’
> >   Size: 0               Blocks: 0          IO Block: 4096   directory
> > 
> > Device: 2bh/43d Inode: 3834720     Links: 1
> > Access: (0755/drwxr-xr-x)  Uid: ( 1000/     asn)   Gid: (  100/   users)
> > Access: 2013-11-08 11:54:32.431040963 +0100
> > Modify: 2013-11-08 11:54:32.430040956 +0100
> > Change: 2013-11-08 11:54:32.430040956 +0100
> > 
> >  Birth: -
> > 
> > then you see Links: 1. On ext4 or other filesystems:
> > 
> > mkdir x
> > stat x
> > 
> >   File: ‘x’
> >   Size: 4096            Blocks: 8          IO Block: 4096   directory
> > 
> > Device: fd00h/64768d    Inode: 8126886     Links: 2
> > Access: (0755/drwxr-xr-x)  Uid: ( 1000/     asn)   Gid: (  100/   users)
> > Access: 2013-11-08 11:54:55.428212340 +0100
> > Modify: 2013-11-08 11:54:55.427212319 +0100
> > Change: 2013-11-08 11:54:55.427212319 +0100
> > 
> >  Birth: -
> > 
> > the link count for a directory differs: Links: 2.
> > 
> > Why is btrfs different here? Could someone explain this?
> 
> As I understand it, inferring the number of directory entries from
> st_nlink is an optimization that isn't universally valid. If that
> count is 1, it must be considered invalid, and programs that don't
> handle this correctly are broken.  Coreutils handle this, at least...

Thanks for the explanation, I will fix our code.


	-- andreas

-- 
Andreas Schneider                   GPG-ID: CC014E3D
www.cryptomilk.org                asn@cryptomilk.org


      reply	other threads:[~2013-11-08 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 11:07 btrfs and default directory link count Andreas Schneider
2013-11-08 12:24 ` cwillu
2013-11-08 14:11   ` Andreas Schneider [this message]

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=13844973.BJjIDpTNz7@magrathea \
    --to=asn@cryptomilk.org \
    --cc=cwillu@cwillu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=samba-technical@lists.samba.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