The partition is a physical ~5GB --mixed lzo compressed partition.
The kernel 2.6.39-rc1 + reverted commit
c59021f846881a957ac5afe456d0f59d6a517b61.
(see http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg09083.html)
This time I've really filled whole partition and kernel OOpsed.
Note,
On Sat, 02 Apr 2011 17:37:58 +0800
liubo liubo2...@cn.fujitsu.com wrote:
On 04/02/2011 05:19 PM, Sergei Trofimovich wrote:
The partition is a physical ~5GB --mixed lzo compressed partition.
The kernel 2.6.39-rc1 + reverted commit
c59021f846881a957ac5afe456d0f59d6a517b61.
(see
On 04/02/2011 06:41 PM, Sergei Trofimovich wrote:
On Sat, 02 Apr 2011 17:37:58 +0800
liubo liubo2...@cn.fujitsu.com wrote:
On 04/02/2011 05:19 PM, Sergei Trofimovich wrote:
The partition is a physical ~5GB --mixed lzo compressed partition.
The kernel 2.6.39-rc1 + reverted commit
On Fri, 2011-04-01 at 09:34 -0400, Christoph Hellwig wrote:
On Thu, Mar 31, 2011 at 08:02:22AM -0400, Chris Mason wrote:
Excerpts from Christoph Hellwig's message of 2011-03-31 02:36:36 -0400:
On Thu, Mar 31, 2011 at 12:00:11AM -0400, Larry D'Anna wrote:
This is a simple patch to allow
Hallo,
if I've understood some mails in this list correct, then btrfs needs a
character device btrfs-control with the ID 10:55
When I look for this device in
/sys/class/misc/btrfs-control/dev
I see 10:234
And when I run the command
mkfs.btrfs -d raid0 -m raid1 /dev/sda1
* Ken Drummond (bt...@kendrummond.com) [110402 11:51]:
I don't really understand the details here, but doesn't the creation of
a snapshot already lead to data extents being shared between
sub-volumes? From a simple user perspective this sounds like a very
useful capability.
I was surprised
On Sat, Apr 02, 2011 at 06:45:00PM +0200, Helmut Hullen wrote:
if I've understood some mails in this list correct, then btrfs needs a
character device btrfs-control with the ID 10:55
When I look for this device in
/sys/class/misc/btrfs-control/dev
I see 10:234
Kernel
Hallo, Tomasz,
Du meintest am 02.04.11:
No udev is wrong.
Sorry - no.
On the machines I use I don't need udev (they are a kind of server, not
end user workstations with often changing hardware). And I could abstain
(? - please excuse my gerlish) from btrfs, but not from fixed device
I am very happy to see this patch. It was one of the first thing I
tried after making a subvolume, cp --reflink, and it failed. I'll have
to try this out.
Jérôme Poulin
On 2011-04-02, at 12:56, Larry D'Anna la...@elder-gods.org wrote:
* Ken Drummond (bt...@kendrummond.com) [110402 11:51]:
I
On Tue, 29 Mar 2011 10:32:24 +0300
Sergei Trofimovich sly...@gmail.com wrote:
The partition is a physical ~5GB --mixed lzo compressed partition.
I run large compiles there. During one of those kernel OOpsed
(It seems to be reproducible). At the time of OOps and after reboot 'du -hs'
reports
Goffredo Baroncelli wrote:
If you don't want to use udev you have two choices:
- use devtmpfs
- create manually a device. But nobody guarantee that the minor/major
will not change.
- use a udev replacement intended for embedded systems, such as mdev
//Peter
--
To unsubscribe from this
Hallo, Goffredo,
Du meintest am 03.04.11:
if I've understood some mails in this list correct, then btrfs needs
a character device btrfs-control with the ID 10:55
When I look for this device in
/sys/class/misc/btrfs-control/dev
I see 10:234
As wrote by Tomasz the minor number
Hallo, Peter,
Du meintest am 03.04.11:
If you don't want to use udev you have two choices:
- use devtmpfs
- create manually a device. But nobody guarantee that the
minor/major will not change.
- use a udev replacement intended for embedded systems, such as mdev
13 matches
Mail list logo
