On Tue, Jul 30, 2013 at 7:40 AM, Miao Xie mi...@cn.fujitsu.com wrote:
On mon, 29 Jul 2013 11:48:32 +0400, Azat Khuzhin wrote:
On Sat, Jul 27, 2013 at 2:12 PM, Azat Khuzhin a3at.m...@gmail.com wrote:
Replace list_for_each_entry() by list_for_each_entry_safe() in
__btrfs_close_devices()
There
http://repo.or.cz/w/btrfs-progs-unstable/devel.git/shortlog/refs/heads/dev/dev-add-notrim
Please base your patch on top of that or after when they hit the
mailinglist/integration.
it makes sense to write patch on top of this. I would wait.
Anand
david
--
To unsubscribe from this list:
Hi,
I'm using LK3.10, replaying filesystem traces on a btrfs filesystem,
and I my experiments always result in write()'s returning ENOSPC
(No space left on device). I'm baffled because I've been reading
about this issue on here, but in those other cases there were
indications that the Metadata
Hello list,
I have a 5 drive raid10 setup (6th sata port malfunctions, all drives
are 3TB in size).
I want to remove a single drive, yet the 'btrfs device delete' command
gives me the unable to go below four devices on raid10 error.
This is the result after first deleting a device, after a
How would I determine when this situation is approaching? On all important
systems I have cron jobs and nagios checks to determine via df when thw file
system is about to run out of space. How do I do the same for this condition?
Chris Murphy li...@colorremedies.com wrote:
On Aug 26, 2013,
On fri, 30 Aug 2013 15:46:43 +0100, Filipe David Borba Manana wrote:
When the binary search returns 0 (exact match), the target key
will necessarily be at slot 0 of all nodes below the current one,
so in this case the binary search is not needed because it will
always return 0, and we
Steven Post posted on Sat, 31 Aug 2013 12:12:55 +0200 as excerpted:
Btrfs Btrfs v0.19
The system is running Debian Wheezy (kernel 3.2.0-4-amd64 #1 SMP Debian
3.2.46-1 x86_64).
Is this something known (and possibly resolved in a later version), or
should I open a bug report about it? Could
When the binary search returns 0 (exact match), the target key
will necessarily be at slot 0 of all nodes below the current one,
so in this case the binary search is not needed because it will
always return 0, and we waste time doing it, holding node locks
for longer than necessary, etc.
Below
On Fri, Aug 30, 2013 at 10:14:01AM -0400, Josef Bacik wrote:
Btrfs uses an rwsem to control access to its extent tree. Threads will hold a
read lock on this rwsem while they scan the extent tree, and if need_resched()
they will drop the lock and schedule. The transaction commit needs to take
On Aug 31, 2013, at 3:04 AM, Russell Coker russ...@coker.com.au wrote:
How would I determine when this situation is approaching? On all important
systems I have cron jobs and nagios checks to determine via df when thw file
system is about to run out of space. How do I do the same for this
On Aug 31, 2013, at 4:12 AM, Steven Post redalert.comman...@gmail.com wrote:
The system is running Debian Wheezy (kernel 3.2.0-4-amd64 #1 SMP Debian
3.2.46-1 x86_64).
Is this something known (and possibly resolved in a later version), or
should I open a bug report about it?
Try 3.10 or
Hi,
I have a 9 disk raid1 filesystem that is no longer mountable.
I am using ubuntu 13.04 with kernel 3.8.0-26-generic
What happened was that I was removing a device using
btrfs device delete
and this was running for quite a while (I was removing a 3T device)
but eventually this failed with the
ronnie sahlberg posted on Sat, 31 Aug 2013 14:50:36 -0700 as excerpted:
And while btrfsck eventually does complete the filesystem remains
unmountable.
Any advice ?
This isn't specific to your question, but in general...
In the Question: How can I recover this partition? (unable to find
On Sat, Aug 31, 2013 at 11:42:28AM -0600, Chris Murphy wrote:
On Aug 31, 2013, at 4:12 AM, Steven Post redalert.comman...@gmail.com wrote:
The system is running Debian Wheezy (kernel 3.2.0-4-amd64 #1 SMP Debian
3.2.46-1 x86_64).
Is this something known (and possibly resolved in a
On Aug 31, 2013, at 4:01 PM, Duncan 1i5t5.dun...@cox.net wrote:
ronnie sahlberg posted on Sat, 31 Aug 2013 14:50:36 -0700 as excerpted:
And while btrfsck eventually does complete the filesystem remains
unmountable.
Any advice ?
This isn't specific to your question, but in general...
On Sat, 2013-08-31 at 11:42 -0600, Chris Murphy wrote:
On Aug 31, 2013, at 4:12 AM, Steven Post redalert.comman...@gmail.com wrote:
The system is running Debian Wheezy (kernel 3.2.0-4-amd64 #1 SMP Debian
3.2.46-1 x86_64).
Is this something known (and possibly resolved in a later
On Aug 31, 2013, at 5:55 PM, Steven Post redalert.comman...@gmail.com wrote:
On Sat, 2013-08-31 at 11:42 -0600, Chris Murphy wrote:
Yes. It might take a few minutes after the chunks are reallocated for the
device to be removed from the volume. I've had some cases where even a
reboot was
17 matches
Mail list logo
