All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dipl.-Ing. Michael Niederle" <mniederle@gmx.at>
To: kreijack@libero.it
Cc: kreijack@gmail.com, linux-btrfs@vger.kernel.org
Subject: Re: Missing entry for updated directory
Date: Sat, 27 Mar 2010 22:19:53 +0100	[thread overview]
Message-ID: <20100327221953.35781dcd@simplux> (raw)
In-Reply-To: <201003272047.30636.kreijack@libero.it>

Hi, Goffredo!

I checked all btrfs-item types (changed sk->max_type to 255 and removed the
filtering) connected with the updated directory's inode.

But none of them had got a new generation number.

I found the missing directory only using a more conventional tool that checked
all files and directories in both snapshots.

Here the output from stat:

>stat 2010-03-21/root/.googleearth/Temp/.kmztmp/
  File: `2010-03-21/root/.googleearth/Temp/.kmztmp/'
  Size: 21340     	Blocks: 0          IO Block: 4096   directory
Device: 15h/21d	Inode: 31757       Links: 1
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2010-02-19 22:12:25.339932662 +0100
Modify: 2009-11-18 13:45:52.000000000 +0100
Change: 2010-01-12 19:48:01.911913031 +0100

>stat 2010-03-22/root/.googleearth/Temp/.kmztmp/
  File: `2010-03-22/root/.googleearth/Temp/.kmztmp/'
  Size: 21268     	Blocks: 0          IO Block: 4096   directory
Device: 16h/22d	Inode: 31757       Links: 1
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2010-02-19 22:12:25.339932662 +0100
Modify: 2010-03-21 21:49:16.512553912 +0100
Change: 2010-03-21 21:49:16.512553912 +0100

Greetings, Michael

  reply	other threads:[~2010-03-27 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27 11:04 Missing entry for updated directory Dipl.-Ing. Michael Niederle
2010-03-27 19:47 ` Goffredo Baroncelli
2010-03-27 21:19   ` Dipl.-Ing. Michael Niederle [this message]
2010-03-27 22:13     ` Goffredo Baroncelli

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=20100327221953.35781dcd@simplux \
    --to=mniederle@gmx.at \
    --cc=kreijack@gmail.com \
    --cc=kreijack@libero.it \
    --cc=linux-btrfs@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.