Well, the mail still says the truth :)
On 7/10/11 11:57 AM, Helmut Hullen wrote:
Hallo, Felix,
Du meintest am 10.07.11:
I'll be quiet about this topic now. I've to admit that I was a little
bit drunk yesterday. Sorry again!
Don't drink and write!
Viele Gruesse!
Helmut
--
To unsubscribe fro
Hallo, Felix,
Du meintest am 10.07.11:
> I'll be quiet about this topic now. I've to admit that I was a little
> bit drunk yesterday. Sorry again!
Don't drink and write!
Viele Gruesse!
Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to m
You don't understood me. Ofc the developer need bug reports and all that
stuff. But it's the way youre doing it. Imho a lot of your mails sounds
like the only goal of them are to punish btrfs.
Maybe I'm the only one who feels this way, then I'm sorry. I'll be quite
about this topic now. I've t
On 07/09/2011 07:28 PM, cac...@quantum-sci.com wrote:
> On Saturday 9 July, 2011 10:12:43 you wrote:
>> If your btrfs lives on two or more devices you will have to run
>> 'btrfs device scan' prior to mount or give all devices as arguments
>> to mount.btrfs.
>
> Ohhh, I'd added a disk drive without
Hallo, Felix,
Du meintest am 10.07.11:
> Did you ever say something positive about btrfs? :D All I read from
> in the last months is complaining about btrfs.
I use it, since many months.
But it's still an adventure, I won't use it for valuable data.
> I'm sorry but it seems that 90% for your co
Did you ever say something positive about btrfs? :D All I read from in
the last months is complaining about btrfs.
In this case it was his fault because he forget to update the fstab. Im
pretty sure it was also your fault when you screwed up your 2.6.38.5
kernel...
I'm sorry but it seems that 90
On Sat, Jul 09, 2011 at 10:28:03AM -0700, cac...@quantum-sci.com wrote:
> On Saturday 9 July, 2011 10:12:43 you wrote:
> > If your btrfs lives on two or more devices you will have to run 'btrfs
> > device scan' prior to mount or give all devices as arguments to mount.btrfs.
>
> Ohhh, I'd added a d
Hallo, Cacook,
Du meintest am 09.07.11:
> Just compiled a custom kernel, but unable to mount a btrfs partition.
> It essentially says 'unrecognized filesystem'. What could be
> missing?
Perhaps you only need a newer kernel. Sounds funny, but some days ago I
had a similar problem, with kerne
On Saturday 9 July, 2011 10:12:43 you wrote:
> If your btrfs lives on two or more devices you will have to run 'btrfs
> device scan' prior to mount or give all devices as arguments to mount.btrfs.
Ohhh, I'd added a disk drive without modifying fstab. Thanks.
Where would you put a device scan to
On 09.07.2011 18:19, cac...@quantum-sci.com wrote:
> Just compiled a custom kernel, but unable to mount a btrfs partition. It
> essentially says 'unrecognized filesystem'. What could be missing?
>
> # File systems
> #
> CONFIG_EXT2_FS=y
> CONFIG_EXT2_FS_XATTR=y
> CONFIG_EXT2_FS_POSIX_ACL=y
> CON
Just compiled a custom kernel, but unable to mount a btrfs partition. It
essentially says 'unrecognized filesystem'. What could be missing?
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_F
11 matches
Mail list logo