similar to: Resize command syntax wrong?

Hi, My company is testing btrfs (kernel 2.6.38) on a slave MySQL database server with a 195Gb filesystem (of which about 123Gb is used). So far, we''re quite impressed with the performance. Our database loads are high, and if filesystem performance wasn''t good, MySQL replication wouldn''t be able to keep up and the slave latency would begin to climb. This though, is

Hallo, linux-btrfs, First I create an array of 2 disks with mkfs.btrfs -d raid0 -m raid1 /dev/sdb1 /dev/sdd1 and mount it at /srv/MM. Then I fill it with about 1,6 TByte. And then I add /dev/sde1 via btrfs device add /dev/sde1 /srv/MM btrfs filesystem balance /srv/MM (it run about 20 hours) Then I work on it, copy some new files, delete some old files - all works well. Only df

Hallo, "never change a running system" ... For some months I run btrfs unter kernel 3.2.5 and 3.2.9, without problems. Yesterday I compiled kernel 3.3.4, and this morning I started the machine with this kernel. There may be some ugly problems. Copying something into the btrfs "directory" worked well for some files, and then I got error messages (I''ve not

Hallo, linux-btrfs, please delete the option "-L" (for labelling) in "mkfs.btrfs", in some configurations it doesn''t work as expected. My usual way: mkfs.btrfs -d raid0 -m raid1 /dev/sdb /dev/sdc /dev/sdd ... One call for some devices. Wenn I add the option "-L mylabel" then each device gets the same label, and therefore some other programs

I''ve just pushed out a new integration branch to my git repo. This is purely bugfix patches -- there are no new features in this issue of the integration branch. I''ve got a stack of about a dozen more patches with new features in them still to go. I''ll be working on those tomorrow. As always, there''s minimal testing involved here, but it does at least compile on

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_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y

I have a couple computers running 2.6.38 (Ubuntu Natty 2.6.38-8-generic), and on both of them "btrfs device scan" comes back with nothing other than "failed to read /dev/sr0" One computer has a btrfs RAID-1 volume, and the other has two separate btrfs filesystems. The results are the same whether the filesystems are mounted or not. Why is "btrfs device scan" not

Hallo, linux-btrfs, I can''t switch a running "btrfs filesystem balance ..." via ctrl z bg into the background, with other jobs this way works. The stopping command "ctrl z" doesn''t work. (may be on other keyboards it''s "ctrl y") What goes wrong? Viele Gruesse! Helmut -- To unsubscribe from this list: send the line

Added linux-btrfs and Helmut Hullen, who seemed to experience hangs on a T23 with BTRFS as well, to Cc. Am Thursday 03 February 2011 schrieb Rafael J. Wysocki: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.36 and 2.6.37. > > The following bug entry is on the current list of known regressions > introduced between

Hello If I want to manage a complete disk with btrfs, what''s the "Best Practice"? Would it be best to create the btrfs filesystem on "/dev/sdb", or would it be better to create just one partition from start to end and then do "mkfs.btrfs /dev/sdb1"? Would the same recomendation hold true, if we''re talking about huge disks, like 4TB or so?

Hallo, I''d like to get some explanations ... # btrfs filesystem show Label: ''MMedia'' uuid: 120b036a-883f-46aa-bd9a-cb6a1897c8d2 Total devices 3 FS bytes used 3.80TB devid 1 size 1.82TB used 1.29TB path /dev/sdg1 devid 3 size 1.81TB used 1.29TB path /dev/sdc1 devid 2 size 1.81TB used 1.28TB path /dev/sdb1 Btrfs Btrfs v0.19 # btrfs filesystem df /srv/MM

Hallo, linux-btrfs, I''m working with btrfs for some days. btrfs-progs-20101101, kernel 2.6.35.8 (both self compiled). First step: mkfs.btrfs /dev/sdd1 mount /dev/sdd1 /srv/MM for a 2 TByte partition, worked well. Copying about 1,5 TByte data to this partition worked well. Second step: btrfs device add /dev/sdc1 /srv/MM btrfs filesystem balance

Dear all, I wanna create a GNU/Linux that it boots from USB. I don't any idea on that. Can you introduce me a doc that i can use it & i can solve my problem? Cheers, -- ------------------------- Mohsen Pahlevanzadeh email address : mohsen at pahlevanzadeh.org web site : http://pahlevanzadeh.org IRC IM : m_pahlevanzadeh yahoo IM : linuxorbsd ----------------------------

Hi! The problem is that the BTRFS raid10 filesystem without any understandable cause refuses to mount. Here is dmesg output: [77847.845540] device label linux-btrfs-raid10 devid 3 transid 45639 /dev/sdc1 [77848.633912] btrfs: allowing degraded mounts [77848.633917] btrfs: enabling auto defrag [77848.633919] btrfs: use lzo compression [77848.633922] btrfs: turning on flush-on-commit [77848.658879]

Hallo, Luke, Du meintest am 02.04.16: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE Perhaps a max protocol = NT1 in the global section helps. And

Is that with an active directory domain controller? On Apr 3, 2016 11:21 PM, "barış tombul" <bbtombul at gmail.com> wrote: > my conf win10 no problem: > client NTLMv2 auth = Yes > client lanman auth = No > server max protocol = SMB3_11 > server min protocol = LANMAN1 > client max protocol = SMB3_11 > client min protocol = CORE > >

Hi, I''m hitting this issue - sda5 is a normal device, nothing to do with loop, encryption etc. # mkfs.btrfs /dev/sda5 WARNING! - Btrfs v0.19-35-g1b444cd-dirty IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using error checking /dev/sda5 mount status Is there something I can do to resolve this? Thank you Lubos -- To unsubscribe from this list: send the line

Hi Helmut, Thank you for your mail. The distribution is Debian linux 7.9. I am talking of a fresh installation, and of course of it's update after. Thank you for helping. Regards Le 19 avr. 2016 06:08, "Helmut Hullen" <Hullen at t-online.de> a écrit : > Hallo, Jules, > > Du meintest am 18.04.16: > > > Is it recommended to install the tarball or archive

Hi there... I have kernel version 2.6.36.3, compiled with gcc 4.4.5, btrfstools version 0.19+20101101 I have a btrfs filesystem (/data) consisting of two 1TB hard disks, raid0. I added in another 1TB hard drive. root@X86-64:~# btrfs filesystem show failed to read /dev/sdh failed to read /dev/sdg failed to read /dev/sdf failed to read /dev/sde failed to read /dev/sr0 failed to read /dev/fd0u800

Hallo, H. Peter, Du meintest am 25.06.13: >> We could probably fabricate a script of some sort to check for the >> required version of gnu-efi, and skip it if not found, unless the >> user explicitly requested that the EFI files be built, in which case >> we'd error out. >> >> Thoughts? > Not really... let's just document "make bios". By