Btrfs devel - Mar 2013 - The limitation of 1024 extends of btrfs restore seems to smal

Hi all,

I have recently tried to restore a btrfs partition that was mounted as
"/home".

The "btrfs restore" keep asking annoying questions like "we seem
to
loop deep...", and I have to use "yes ''n'' | btrfs
restore" to bypass
this.

But I was interesting what kind of files that have such a problem. So
I downloaded btrfs source code and looked at it. By adding additional
print point to the output, I proved that all the problematic files
just have too many (more than 1024) extends. Furthermore, I listed all
problematic files into a file. The result shows that all those files
falls in the following categories:

1. Firefox related files
       .mozilla/firefox/c6tw6z0l.default/urlclassifier3.sqlite
       .mozilla/firefox/6huj12lo.default/Cache/_CACHE_???_

2. Google earth cache file
      .googleearth/Cache/dbCache.dat

3. aMule download files (Temp or Incoming)

4. Transmission download files (part files or full files)

Base on my knowledge about the above applications, I believe that it
is natural for those files to have more than 1024 extends. So why the
official "btrfs restore" shall alert the user about those files? and
not even provides an option to bypass it?

It is easy to provide a patch since the "1024" is a easy to find hard
coded value. However I want to know why this limitation even exists.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html