On 04/13/2012 02:53 PM, Arne Jansen wrote:
> On 13.04.2012 05:40, Liu Bo wrote:
>> > On 04/12/2012 11:54 PM, Arne Jansen wrote:
>>> >> This patchset reimplements snapshot deletion with the help of the
>>> >> readahead
>>> >> framework. For this callbacks are added to the framework. The main idea
On 13.04.2012 09:10, Liu Bo wrote:
> On 04/13/2012 02:53 PM, Arne Jansen wrote:
>
>> On 13.04.2012 05:40, Liu Bo wrote:
On 04/12/2012 11:54 PM, Arne Jansen wrote:
>> This patchset reimplements snapshot deletion with the help of the
>> readahead
>> framework. For this callbacks ar
On 04/13/2012 03:10 PM, Liu Bo wrote:
> On 04/13/2012 02:53 PM, Arne Jansen wrote:
>
>> On 13.04.2012 05:40, Liu Bo wrote:
On 04/12/2012 11:54 PM, Arne Jansen wrote:
>> This patchset reimplements snapshot deletion with the help of the
>> readahead
>> framework. For this callback
On 04/13/2012 03:19 PM, Arne Jansen wrote:
>
> might be out of memory. How much does this vm (?) have?
> Can you try to reduce the constants in disk-io.c:2003-2005?
>
> Thanks,
> Arne
>
Seems not related to an OOM:
# free -m
total used free sharedbuffers c
Hello,
Using find-new, I've seen that all regular extents seem to be 4k
aligned. Inline extents were not aligned.
Is it guaranteed that all regular extents are 4k aligned in
disk_bytenr, disk_num_bytes, offset and num_bytes? Even if COW or what
ever may happen happens?
Thanks,
Alex.
--
To unsubsc
Avoid calling free_extent_buffer more than once when the iterator function
returns non-zero. The only code that uses this is scrub repair for corrupted
nodatasum blocks.
Signed-off-by: Jan Schmidt
---
fs/btrfs/backref.c |8 +++-
1 files changed, 3 insertions(+), 5 deletions(-)
diff --gi
iref_to_path and iterate_irefs both increment the eb's refcount to use it
after releasing the path. Both depend on consistent data remaining in the
extent buffer and need a read lock to protect it.
Signed-off-by: Jan Schmidt
---
fs/btrfs/backref.c | 17 +++--
1 files changed, 15 in
On 13.04.2012 09:20, Liu Bo wrote:
> On 04/13/2012 03:10 PM, Liu Bo wrote:
>
>> On 04/13/2012 02:53 PM, Arne Jansen wrote:
>>
>>> On 13.04.2012 05:40, Liu Bo wrote:
>>
>>
>> I see.
>>
>> I've just tested it on 3.4-rc2, I cannot get it through due to the
>> following, could you take a look?
>>
>>
I originally created a RAID1(0) compound out of 4 drives. One of them
[sdf] failed recently and was removed. The filesystem is no longer
mountable with the 3 drives left.
On 3.3.1:
# btrfs dev scan
[ 1065.572938] device label srv devid 1 transid 11386 /dev/sdc
[ 1065.573044] device label srv de
On Fri, Apr 13, 2012 at 12:55:43PM +0200, Jan Engelhardt wrote:
>
> I originally created a RAID1(0) compound out of 4 drives. One of them
> [sdf] failed recently and was removed. The filesystem is no longer
> mountable with the 3 drives left.
> On 3.3.1:
>
> # btrfs dev scan
> [ 1065.572938] de
On Fri, Apr 13, 2012 at 8:49 AM, cwillu wrote:
>> dmesg and fstab attached as requested.
>
> Need dmesg after you've hit alt-sysrq-w a couple times during the slow period.
here.
i guess i should also increase dmesg history size next time.
other than the slow boot, everything seems normal after 1
# df
/dev/sdd5860554336 2651644680 20368600 100% /top.srv
# btrfs scrub status /top.srv
[ 4877.298065] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 4877.298122] IP: [] strncpy+0x7/0x1f
[ 4877.298159] PGD 193cc067 PUD accb067 PMD 0
[ 4877.298191] Oo
On Friday 13 April 2012 20:58:22 Hugo Mills wrote:
>I think you need "-o degraded" in this case.
I've always wondered why btrfs doesn't fall back to this by default if
it fails to find a device, would seem the obvious thing to do (we
don't have to tell mdadm if a disk has gone away for inst
http://comments.gmane.org/gmane.comp.file-systems.btrfs/16302
> btrfsprogs identifies itself only as "v0.19+".
so it's opensuse version, blaming myself. starting with the next update
there will be a date tag.
david
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the
Hi!
This is what happened while rsyncing my system disk to my btrfs backup
device after I enabled space caching for the latter (and first time using it
after 3.3.1, last time I sync'ed it was with 3.2.x):
# mount options
# LABEL=usb-backup /mnt/usb-backup btrfs \
# compress-force=zlib,subvoli
These are usb disks? Does that failure at 12.241517 (or related)
happen every time?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Apr 12, 2012 at 10:56:00PM +, Duncan wrote:
> Hugo Mills posted on Thu, 12 Apr 2012 22:55:46 +0100 as excerpted:
> > The general advice is -- use a single-device root filesystem, or an
> > initramfs. These are simple, supported, and will generally get good
> > help. Any other configurat
On Fri, Apr 13, 2012 at 2:57 PM, cwillu wrote:
> These are usb disks? Does that failure at 12.241517 (or related)
> happen every time?
no, 0CCD:0052 is the webcam. i dont have the modules for the webcam
in initramfs, thats why.
the real slowness is around 33.305370
The 2 SATA Disks are fine. I
Hi Linus,
My for-linus branch has btrfs fixes and updates:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
The top commit is the only one that isn't strictly a bug fix. It
updates the btrfs metadata checker code to support metadata blocks
larger than the page size.
On Friday 2012-04-13 12:58, Hugo Mills wrote:
>On Fri, Apr 13, 2012 at 12:55:43PM +0200, Jan Engelhardt wrote:
>>
>> I originally created a RAID1(0) compound out of 4 drives. One of them
>> [sdf] failed recently and was removed. The filesystem is no longer
>> mountable with the 3 drives left.
>
On Fri, Apr 13, 2012 at 02:26:19PM +0200, Ahmet Inan wrote:
> On Fri, Apr 13, 2012 at 1:22 PM, Ahmet Inan
> wrote:
> > On Fri, Apr 13, 2012 at 8:49 AM, cwillu wrote:
> >>> dmesg and fstab attached as requested.
> >>
> >> Need dmesg after you've hit alt-sysrq-w a couple times during the slow
> >>
On 4/12/2012 11:25 PM, Travis Shivers wrote:
> A few months ago, my btrfs storage array became corrupted because of a
> power failure. A while ago, I made this thread to try and resolve the
> problem. (http://www.digipedia.pl/usenet/thread/11904/15955/) You can
> find detailed information about the
Fix a bug, where in case we need to adjust stripe_size so that the
length of the resulting chunk is less than or equal to max_chunk_size,
DUP chunks turn out to be only half as big as they could be.
Cc: Arne Jansen
Signed-off-by: Ilya Dryomov
---
fs/btrfs/volumes.c |6 --
1 files change
On 13.04.2012 16:05, Ilya Dryomov wrote:
> Fix a bug, where in case we need to adjust stripe_size so that the
> length of the resulting chunk is less than or equal to max_chunk_size,
> DUP chunks turn out to be only half as big as they could be.
>
> Cc: Arne Jansen
> Signed-off-by: Ilya Dryomov
On Thu, Apr 12, 2012 at 09:56:30PM +, Francesco Cepparo wrote:
> On Thu, Apr 12, 2012 at 6:20 PM, Josef Bacik wrote:
> > On Thu, Apr 12, 2012 at 02:15:25PM -0400, Chris Mason wrote:
> >> On Thu, Apr 12, 2012 at 02:08:37PM -0400, Josef Bacik wrote:
> >> > On Wed, Apr 11, 2012 at 11:59:43PM +000
Actually, I was running 3.0.0-16 when the power failure occurred. I
upgraded to 3.2.8 shortly after the corruption occurred to see if it
would fix the corruption. I really do not care about completely
repairing or being able to mount the filesystem since I would just
like to get my data off the arr
commit 7a3ae2f8c8c8432e65467b7fc84d5deab04061a0 upstream.
In commit 4692cf58 (Linux 3.3) we introduced new backref walking code for
btrfs. This assumes we're searching live roots, which requires a transaction
context. While scrubbing, however, we must not join a transaction because
this could dead
On Fri, Apr 13, 2012 at 04:58:15PM +0200, Jan Schmidt wrote:
> commit 7a3ae2f8c8c8432e65467b7fc84d5deab04061a0 upstream.
>
> In commit 4692cf58 (Linux 3.3) we introduced new backref walking code for
> btrfs. This assumes we're searching live roots, which requires a transaction
> context. While scr
Hello!
Is there any documentation about btrfs mount flags wrt:
1. which flags are one-time options and are permanent,
2. which flags are global per btrfs partition,
3. which flags are local per subvolume mount?
I'm asking because while googling I found very confusing info about
autodefrag. Some
On Fri, Apr 13, 2012 at 08:25:59AM -0700, Greg KH wrote:
> On Fri, Apr 13, 2012 at 04:58:15PM +0200, Jan Schmidt wrote:
> > commit 7a3ae2f8c8c8432e65467b7fc84d5deab04061a0 upstream.
> >
> > In commit 4692cf58 (Linux 3.3) we introduced new backref walking code for
> > btrfs. This assumes we're sear
Just in case it is interesting, here's the blocked state (take note I
currently have other fs actions running on my btrfs root fs copying a lot of
files from a remote server):
Kai Krakow schrieb:
> This is what happened while rsyncing my system disk to my btrfs backup
> device after I enabled
Kai Krakow posted on Fri, 13 Apr 2012 17:50:45 +0200 as excerpted:
> Is there any documentation about btrfs mount flags wrt:
AFAIK the best documentation is the wiki, which you didn't mention, tho
you mentioned google. It's also possible that you found the old/outdated
(because it's read-only
Hugo Mills posted on Fri, 13 Apr 2012 14:16:32 +0100 as excerpted:
> On Thu, Apr 12, 2012 at 10:56:00PM +, Duncan wrote:
>> Hugo Mills posted on Thu, 12 Apr 2012 22:55:46 +0100 as excerpted:
>> > The general advice is -- use a single-device root filesystem, or an
>> > initramfs. These are simp
> From: Sergei Trofimovich
>
> CC: Chris Mason
> Signed-off-by: Sergei Trofimovich
> ---
> Makefile |6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
Ping.
--
Sergei
signature.asc
Description: PGP signature
On Fri, Apr 13, 2012 at 12:48 PM, Duncan <1i5t5.dun...@cox.net> wrote:
> Hugo Mills posted on Fri, 13 Apr 2012 14:16:32 +0100 as excerpted:
>
>> On Thu, Apr 12, 2012 at 10:56:00PM +, Duncan wrote:
>>> Hugo Mills posted on Thu, 12 Apr 2012 22:55:46 +0100 as excerpted:
>>> > The general advice is
Jan Engelhardt posted on Fri, 13 Apr 2012 15:42:14 +0200 as excerpted:
> On Friday 2012-04-13 12:58, Hugo Mills wrote:
>>On Fri, Apr 13, 2012 at 12:55:43PM +0200, Jan Engelhardt wrote:
>>>
>>> I originally created a RAID1(0) compound out of 4 drives. One of them
>>> [sdf] failed recently and was
cwillu posted on Fri, 13 Apr 2012 14:03:38 -0600 as excerpted:
> The fact is that you _don't_ know that your device names aren't going to
> change one day, any more than a generation of developers who only worked
> with ext3 knew that "fsync is expensive and all you really need is the
> atomic gua
Am Freitag, 13. April 2012 schrieb Kai Krakow:
> Hello!
Hi!
> Is there any documentation about btrfs mount flags wrt:
>
> 1. which flags are one-time options and are permanent,
> 2. which flags are global per btrfs partition,
> 3. which flags are local per subvolume mount?
>
> I'm asking becaus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please excuse my ignorance here, but I wondered if this could be a BTRFS
related issue... and perhaps one which might not often be spotted if it is.
A friend of mine has been having trouble with a backup application on a
BTRFS filesystem, and recent
That did it :) the kernel now fails the mounting gracefully as it did before. :)
Thanks!
On Fri, Apr 13, 2012 at 2:45 PM, Josef Bacik wrote:
> On Thu, Apr 12, 2012 at 09:56:30PM +, Francesco Cepparo wrote:
>> On Thu, Apr 12, 2012 at 6:20 PM, Josef Bacik wrote:
>> > On Thu, Apr 12, 2012 at
40 matches
Mail list logo
