Duncan <1i5t5.duncan cox.net> writes:
>
> Jon Nelson posted on Fri, 21 Mar 2014 19:00:51 -0500 as excerpted:
>
> > Using openSUSE 13.1 on x86_64 which - as of this writing - is 3.11.10,
> > Would a more recent kernel than 3.11 have done me any good?
>
> [Reorder
Using openSUSE 13.1 on x86_64 which - as of this writing - is 3.11.10,
I tried to copy a bunch of files over to a btrfs filesystem (which was
mounted as /, in fact).
After some time, things ground to a halt and I got out of disk space errors.
btrfs fi df / showed about 1TB of *data* free, and 50
On Wed, Jul 17, 2013 at 6:04 PM, Josef Bacik wrote:
> On Wed, Jul 17, 2013 at 05:44:23PM -0500, Jon Nelson wrote:
>> I had a btrfs filesystem under 3.9.8 that failed /hard/ today. So hard
>> that the filesystem could not be mounted because there wasn't enough
>> free sp
I had a btrfs filesystem under 3.9.8 that failed /hard/ today. So hard
that the filesystem could not be mounted because there wasn't enough
free space, unless it was mounted read only.
This happened after I ran out of metadata space (is there a way to
increase the amount of metadata storage) while
On Fri, Jun 21, 2013 at 6:30 AM, Chris Mason wrote:
> Quoting Jon Nelson (2013-06-20 21:46:46)
>> Is this what you are looking for?
>> After this, the CPU gets "stuck" and I have to reboot.
>>
>>
>> [360491.932226] [ cut here ]---
wind+0x23b/0x240 [btrfs]
[360491.935233] RSP
[360491.946047] ---[ end trace 1475a0830dcadf9c ]---
[360491.946051] note: btrfs-endio-wri[22166] exited with preempt_count 1
On Thu, Jun 20, 2013 at 8:11 PM, Chris Mason wrote:
> Quoting Jon Nelson (2013-06-18 13:19:04)
>> Josef Ba
Josef Bacik fusionio.com> writes:
>
> On Tue, Jun 11, 2013 at 11:43:30AM -0400, Sage Weil wrote:
> > I'm also seeing this hang regularly with both 3.9 and 3.10-rc5. Is this
> > is a known problem? In this case there is no powercycling; just a regular
> > ceph-osd workload.
..
I'm able to
Josef Bacik fusionio.com> writes:
..
> Ok well that's not good, I'm not sure how you got a 156 gigabyte block
group,
> but thats why that warning is going off. Can you pull btrfs-image down
from
> here
>
> git://github.com/josefbacik/btrfs-progs.git
What is the difference between this git re
On Tue, Apr 23, 2013 at 10:03 AM, Liu Bo wrote:
>
> Can you please show us where it BUG_ON(or logs) when mounting with "-o
> recovery"?
> (the stack info below seems not to be a resulf of '-o recovery'?)
I have this from 3.8.8:
2013-04-19T21:19:47.060937-05:00 turnip kernel: [ 100.608815] devi
iring a reboot.
I *can* mount this with "-o recovery,ro" but nothing else works.
On Sat, Apr 20, 2013 at 8:20 AM, Jon Nelson wrote:
> Using 3.8.8, I tried mounting with "-o recovery" and "-o
> recovery,nospace_cache" (which shouldn't be any different, if I
p:~/recovery #
Is there a way for me to use btrfs tools to tell the superblock to go
ahead and use backup root #1 in this case?
On Tue, Apr 16, 2013 at 11:44 AM, Jon Nelson wrote:
> Tried to mount with "-o recovery" using 3.8.7. No change. Does
> anybody have any suggestions?
>
On Fri, Apr 19, 2013 at 11:48 PM, Eric Sandeen wrote:
> On 4/19/13 7:11 PM, Jon Nelson wrote:
>> The following is a minor patch to cmds-restore.c
>>
>
> Hi Jon - just a note -
>
> When sending a patch like this, it's best to follow the standard
> patch form
The following is a minor patch to cmds-restore.c
diff --git a/cmds-restore.c b/cmds-restore.c
index c75e187..273c813 100644
--- a/cmds-restore.c
+++ b/cmds-restore.c
@@ -917,14 +917,16 @@ out:
}
const char * const cmd_restore_usage[] = {
- "btrfs restore [options] ",
+ "btrfs resto
Tried to mount with "-o recovery" using 3.8.7. No change. Does
anybody have any suggestions?
On Sat, Apr 13, 2013 at 6:21 PM, Jon Nelson wrote:
> I have a 4-disk btrfs filesystem in "raid1" mode.
> I'm running openSUSE 12.3, 3.7.10, x86_64.
> A few day
I have a 4-disk btrfs filesystem in "raid1" mode.
I'm running openSUSE 12.3, 3.7.10, x86_64.
A few days ago something went wrong and the filesystem re-mounted itself RO.
After reboot, it didn't come up.
After a fair bit of work, I can get the filesystem to mount with "-o
recovery,ro". However, if
On Mon, Apr 1, 2013 at 5:39 PM, anand jain wrote:
>
>>Is there a way to reset the device
>> error count?
>>
>
> there is -z, is it not what you are looking for ?
>
> --
> # btrfs dev stat --help
> usage: btrfs device stats [-z] |
>
> Show current device IO stats. -z to reset stats afterwar
I have a device that is part of a 4-device btrfs "raid1" setup.
I had accidentally jiggled the cable for this device and it started racking
up errors (about 90,000). After fixing the cable (and a scrub), all of
the errors are fixed (woo!), but
the device still shows lots of errors. Is there a way t
I'm running openSUSE 12.3 on x86_64.
I was running a balance:
btrfs balance -dusage=5 -v /
using the latest btrfs tools code from git (as of this writing)
and got a crash:
[304158.496250] btrfs: found 75 extents
[304159.309289] btrfs: relocating block group 2303295684608 flags 17
[304159.839886]
On Thu, Mar 21, 2013 at 11:25 AM, Eric Sandeen wrote:
> On 3/21/13 10:29 AM, Jon Nelson wrote:
>> On Thu, Mar 21, 2013 at 10:11 AM, Eric Sandeen wrote:
>>> On 3/21/13 10:04 AM, Jon Nelson wrote:
>> ...
>>>> 2. the current git btrfs-show and btrfs fi show both
On Thu, Mar 21, 2013 at 10:11 AM, Eric Sandeen wrote:
> On 3/21/13 10:04 AM, Jon Nelson wrote:
...
>> 2. the current git btrfs-show and btrfs fi show both output
>> *different* devices for device with UUID
>> b5dc52bd-21bf-4173-8049-d54d88c82240, and they're both wrong.
I'm running openSUSE 12.3 x86_64 which has an unknown git version, but
reports v0.19.
I'm also supplying the output from git which reports itself as:
v0.20-rc1-253-g7854c8b
The problem is that btrfs-show (git) and btrfs fi show (git) give
/different/ output from each other which is also different
On Sun, Dec 12, 2010 at 8:06 PM, Ted Ts'o wrote:
> On Sun, Dec 12, 2010 at 07:11:28AM -0600, Jon Nelson wrote:
>> I'm glad you've been able to reproduce the problem! If you should need
>> any further assistance, please do not hesitate to ask.
>
> This p
On Sun, Dec 12, 2010 at 6:43 AM, Ted Ts'o wrote:
> On Sun, Dec 12, 2010 at 04:18:29AM -0600, Jon Nelson wrote:
>> > I have one CPU configured in the environment, 512MB of memory.
>> > I have not done any memory-constriction tests whatsoever.
>
> I've finally
On Sat, Dec 11, 2010 at 9:16 PM, Jon Nelson wrote:
> On Sat, Dec 11, 2010 at 7:40 PM, Ted Ts'o wrote:
>> Yes, indeed. Is this in the virtualized environment or on real
>> hardware at this point? And how many CPU's do you have configured in
>> your virtualized env
On Sat, Dec 11, 2010 at 7:40 PM, Ted Ts'o wrote:
> Yes, indeed. Is this in the virtualized environment or on real
> hardware at this point? And how many CPU's do you have configured in
> your virtualized environment, and how memory memory? Is having a
> certain number of CPU's critical for repr
On Fri, Dec 10, 2010 at 10:54 AM, Jon Nelson wrote:
> On Fri, Dec 10, 2010 at 8:58 AM, Jon Nelson wrote:
>> On Fri, Dec 10, 2010 at 12:52 AM, Jon Nelson wrote:
>>> On Thu, Dec 9, 2010 at 8:38 PM, Ted Ts'o wrote:
>>>> On Fri, Dec 10, 2010 at 02:53:30AM +
On Fri, Dec 10, 2010 at 8:58 AM, Jon Nelson wrote:
> On Fri, Dec 10, 2010 at 12:52 AM, Jon Nelson wrote:
>> On Thu, Dec 9, 2010 at 8:38 PM, Ted Ts'o wrote:
>>> On Fri, Dec 10, 2010 at 02:53:30AM +0100, Matt wrote:
>>>>
>>>> Try a kernel
On Fri, Dec 10, 2010 at 12:52 AM, Jon Nelson wrote:
> On Thu, Dec 9, 2010 at 8:38 PM, Ted Ts'o wrote:
>> On Fri, Dec 10, 2010 at 02:53:30AM +0100, Matt wrote:
>>>
>>> Try a kernel before 5a87b7a5da250c9be6d757758425dfeaf8ed3179
>>>
>>> from t
On Thu, Dec 9, 2010 at 8:38 PM, Ted Ts'o wrote:
> On Fri, Dec 10, 2010 at 02:53:30AM +0100, Matt wrote:
>>
>> Try a kernel before 5a87b7a5da250c9be6d757758425dfeaf8ed3179
>>
>> from the tests I've done that one showed the least or no corruption if
>> you count the empty /etc/env.d/03opengl as an a
On Thu, Dec 9, 2010 at 8:00 PM, Chris Mason wrote:
> Excerpts from Mike Fedyk's message of 2010-12-09 20:58:40 -0500:
>> On Thu, Dec 9, 2010 at 5:38 PM, Chris Mason wrote:
>> > Excerpts from Andi Kleen's message of 2010-12-09 18:16:16 -0500:
>> >> > 512MB.
>> >> >
>> >> > 'free' reports 75MB, 419
On Thu, Dec 9, 2010 at 2:13 PM, Ted Ts'o wrote:
> On Thu, Dec 09, 2010 at 12:10:58PM -0600, Jon Nelson wrote:
>>
>> You should be OK, there. Are you using encryption or no?
>> I had difficulty replicating the issue without encryption.
>
> Yes, I'm using encryp
On Thu, Dec 9, 2010 at 12:01 PM, Ted Ts'o wrote:
> On Tue, Dec 07, 2010 at 09:37:20PM -0600, Jon Nelson wrote:
>> One difference is the location of the transaction logs (pg_xlog). In
>> my case, /var/lib/pgsql/data *is* mountpoint for the test volume
>> (actually, i
On Tue, Dec 7, 2010 at 9:37 PM, Jon Nelson wrote:
> On Tue, Dec 7, 2010 at 1:35 PM, Ted Ts'o wrote:
>> On Tue, Dec 07, 2010 at 01:22:43PM -0500, Mike Snitzer wrote:
>>> > 1. create a database (from bash):
>>> >
>>> > createdb test
>>>
On Tue, Dec 7, 2010 at 2:41 PM, Chris Mason wrote:
> Excerpts from Jon Nelson's message of 2010-12-07 15:25:47 -0500:
>> On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason wrote:
>> > Excerpts from Jon Nelson's message of 2010-12-07 14:34:40 -0500:
>> >> On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason
>>
On Tue, Dec 7, 2010 at 1:35 PM, Ted Ts'o wrote:
> On Tue, Dec 07, 2010 at 01:22:43PM -0500, Mike Snitzer wrote:
>> > 1. create a database (from bash):
>> >
>> > createdb test
>> >
>> > 2. place the following contents in a file (I used 't.sql'):
>> >
>> > begin;
>> > create temporary table foo as s
On Tue, Dec 7, 2010 at 3:02 PM, Chris Mason wrote:
> Excerpts from Jon Nelson's message of 2010-12-07 15:48:58 -0500:
>> On Tue, Dec 7, 2010 at 2:41 PM, Chris Mason wrote:
>> > Excerpts from Jon Nelson's message of 2010-12-07 15:25:47 -0500:
>> >> On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason
>>
On Tue, Dec 7, 2010 at 1:35 PM, Ted Ts'o wrote:
> On Tue, Dec 07, 2010 at 01:22:43PM -0500, Mike Snitzer wrote:
>> > 1. create a database (from bash):
>> >
>> > createdb test
>> >
>> > 2. place the following contents in a file (I used 't.sql'):
>> >
>> > begin;
>> > create temporary table foo as s
On Tue, Dec 7, 2010 at 2:41 PM, Chris Mason wrote:
> Excerpts from Jon Nelson's message of 2010-12-07 15:25:47 -0500:
>> On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason wrote:
>> > Excerpts from Jon Nelson's message of 2010-12-07 14:34:40 -0500:
>> >> On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason
>>
On Tue, Dec 7, 2010 at 2:33 PM, Chris Mason wrote:
> Excerpts from Jon Nelson's message of 2010-12-07 15:25:47 -0500:
>> On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason wrote:
>> > Excerpts from Jon Nelson's message of 2010-12-07 14:34:40 -0500:
>> >> On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason
>>
On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason wrote:
> Excerpts from Jon Nelson's message of 2010-12-07 14:34:40 -0500:
>> On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason wrote:
>> >> postgresql errors. Typically, header corruption but from the limited
>> >> visibility I've had into this via strace, w
On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason wrote:
> Excerpts from Jon Nelson's message of 2010-12-07 13:45:14 -0500:
>> On Tue, Dec 7, 2010 at 12:22 PM, Mike Snitzer wrote:
>> > On Tue, Dec 07 2010 at 1:10pm -0500,
>> > Jon Nelson wrote:
>> >
>>
On Tue, Dec 7, 2010 at 12:22 PM, Mike Snitzer wrote:
> On Tue, Dec 07 2010 at 1:10pm -0500,
> Jon Nelson wrote:
>
>> I finally found some time to test this out. With 2.6.37-rc4 (openSUSE
>> KOTD kernel) I easily encounter the issue.
>>
>> Using a virtual ma
I finally found some time to test this out. With 2.6.37-rc4 (openSUSE
KOTD kernel) I easily encounter the issue.
Using a virtual machine, I created a stock, minimal openSUSE 11.3 x86_64
install, installed all updates, installed postgresql and the 'KOTD'
(Kernel of the Day)
kernel, and ran the foll
On Wed, Dec 1, 2010 at 12:24 PM, Milan Broz wrote:
> On 12/01/2010 06:35 PM, Matt wrote:
>> Thanks for pointing to v6 ! I hadn't noticed that there was a new one :)
>>
>> Well, so I'll restore my box to a working/productive state and will
>> try out v6 (I'm pretty confident that it'll work without
On Fri, Aug 20, 2010 at 7:03 AM, Goffredo Baroncelli wrote:
>
>
> + fprintf(stderr, "ERR-A.11: in command '");
>
> I am not against this kind of error codes, but I prefer
>
> + fprintf(stderr, "Error 'ERR-A.11' in command '");
>
> And a file.txt which de
On Mon, Aug 16, 2010 at 10:15 PM, Jon Nelson wrote:
> Most other directories on /var/cache, *except* those created by squid,
> can be defragmented.
> The filesystem was converted from ext3/4.
>
> turnip:~ # uname -a
> Linux turnip 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +02
Most other directories on /var/cache, *except* those created by squid,
can be defragmented.
The filesystem was converted from ext3/4.
turnip:~ # uname -a
Linux turnip 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 x86_64
x86_64 x86_64 GNU/Linux
(stock openSUSE 11.3 kernel)
turnip:~ btrfsctl
47 matches
Mail list logo
