linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: Force 'btrfs dev scan' not using old libblkid cache
Date: Wed, 16 Apr 2014 09:24:47 +0800	[thread overview]
Message-ID: <534DDBDF.4050408@cn.fujitsu.com> (raw)
In-Reply-To: <20140414162919.GO29256@twin.jikos.cz>


-------- Original Message --------
Subject: Re: [PATCH] btrfs-progs: Force 'btrfs dev scan' not using old 
libblkid cache
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Date: 2014年04月15日 00:29
> On Thu, Apr 10, 2014 at 03:30:21PM +0800, Qu Wenruo wrote:
>> 'btrfs scan' uses libblkid to scan devices by default, and libblkid uses
>> cache to reduce the probe.
>>
>> But if operations below is done in less than 2 seconds(BLKID_PROBE_MIN),
>> 'btrfs scan' will still use the uncorrect cache and scan on the deleted device.
>> 0. /dev/sda[1-4] mounted on /mnt using single data/metadata
>> 1. btrfs dev scan
>> 2. btrfs dev del /dev/sda3 /mnt
>> 3. btrfs dev scan
>>
>> Since the cache made by step 1 is still validated, step 3 will use the
>> cache and consider /dev/sda3 as a btrfs filesystem and try to scan it.
>> But the superblock(at least the first one) is wiped and failed to scan,
>> a error message, which can be avoided and is unneeded, is output.
>>
>> This patch will force scan_for_btrfs() not to use cache to avoid the
>> problem.
>> --- a/utils.c
>> +++ b/utils.c
>> @@ -2057,7 +2057,8 @@ int btrfs_scan_lblkid(int update_kernel)
>>   	blkid_cache cache = NULL;
>>   	char path[PATH_MAX];
>>   
>> -	if (blkid_get_cache(&cache, 0) < 0) {
>> +	/* No to use libblkid cache to avoid old data */
>> +	if (blkid_get_cache(&cache, "/dev/null") < 0) {
> This effectively avoid the blkid cache for all devices but the point of
> blkid was to use it so repeated probes are not done.
>
> I think it's not right to skip the whole cache because one entry may be
> stale, more that we know which one and when.
>
> We should rather explicitly invalidate the removed device after delete,
> I don't what's the right way to do that. Maybe blkid_do_probe() or
> blkid_gc_cache()
Please ignore this patch, since after consulting with libblkid mail 
list, the real problem is that btrfs ioctl for remove device
does not update the mtime/ctime for the device.

Libblkid will only use cache when the device's mtime/ctime stay 
unchanged, if mtime/ctime changed libblkid will do the lowprobe.

I'll try to fix it in kernel space.

Thanks,
Qu


  parent reply	other threads:[~2014-04-16  1:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  7:30 [PATCH] btrfs-progs: Force 'btrfs dev scan' not using old libblkid cache Qu Wenruo
2014-04-10  7:37 ` Anand Jain
2014-04-14 16:29 ` David Sterba
2014-04-15  1:17   ` Qu Wenruo
2014-04-16  1:24   ` Qu Wenruo [this message]
2014-04-16  2:09     ` Qu Wenruo

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=534DDBDF.4050408@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=dsterba@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).