On 04/27/2010 05:46 AM, Chris Mason wrote:
> This oops is fixed in later kernels, and it's why things stopped.
Thanks for the reply. I'm not sure I have the time to give this with
respect to following the trunk kernel right now. If the btrfs project
doesn't have test machines that could be set u
Hello
I've created btrfs on single partition (/dev/sdc3) using:
mkfs.btrfs /dev/sdc3
So far ... it is running fine - but i would like to switch to raid1
configuration.
Unfortunately - i didn't pass any information about raid (-m raid1 -d
raid1) when i created it :(
Now i would like to hot-add
On Fri, Apr 16, 2010 at 20:48, Goffredo Baroncelli wrote:
> Instead the first option has the disadvantage to need to be used for every new
> device.
> From this observation I write a udev rule which scan the new block devices,
> excluding floppy and cdrom.
>
> Below my udev rule
>
> $ cat /etc/ud
>
> On Apr 26, 2010, at 6:18 AM, KOSAK
> > AOP_WRITEPAGE_ACTIVATE was introduced for ramdisk and tmpfs thing
> > (and later rd choosed to use another way).
> > Then, It assume writepage refusing aren't happen on majority pages.
> > IOW, the VM assume other many pages can writeout although the page
On Tue, Apr 27, 2010 at 05:14:26AM -0600, Sean Reifschneider wrote:
> I ported my zfsstress program over to btrfs, and started running it on
> a test machine a few weeks ago. See here for more information and a link
> to the program:
>
>http://www.tummy.com/journals/entries/jafo_20100418_1243
I ported my zfsstress program over to btrfs, and started running it on
a test machine a few weeks ago. See here for more information and a link
to the program:
http://www.tummy.com/journals/entries/jafo_20100418_124309
It looks like after around 8 days of running, there were some issues, as
s
