On 8/9/13 9:04 PM, anand jain wrote:
>
>
>>> btrfs fi show
>>> Label: none uuid: e7aae9f0-1aa8-41f5-8fb6-d4d8f80cdb2c
>>> Total devices 1 FS bytes used 28.00KiB
>>> devid2 size 2.00GiB used 0.00 path /dev/sdc <-- WRONG
>>> devid1 size 2.00GiB used 20.00MiB pa
On Fri, Aug 9, 2013 at 9:46 AM, David Sterba wrote:
> On Fri, Aug 09, 2013 at 01:47:24PM +0800, Miao Xie wrote:
>> On thu, 8 Aug 2013 22:45:48 +0100, Filipe David Borba Manana wrote:
>> > 8MiB is way too large and likely set by mistake. This is not
>> > a significant issue as in practice the max a
On Aug 10, 2013, at 10:17 AM, Chris Murphy wrote:
>
> On Aug 10, 2013, at 9:42 AM, Mike Audia wrote:
>
>> -s 16k
>
> One answer is the drive doesn't expose a 16KB sector. It's basically lying
> when it reports a 512 byte physical sector, but there isn't anything that can
> be done about th
On Aug 10, 2013, at 9:42 AM, Mike Audia wrote:
> -s 16k
One answer is the drive doesn't expose a 16KB sector. It's basically lying when
it reports a 512 byte physical sector, but there isn't anything that can be
done about this on the software side. The other answer:
http://permalink.gmane.o
Wanting to use 16k block for my btrfs, I did so via:
# mkfs.btrfs -l 16k -s 16k -L arch64 -f /dev/sda3
WARNING! - Btrfs v0.20-rc1-253-g7854c8b IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
Detected a SSD, turning off metadata duplication. Mkfs with -m dup if you want
On Aug 10, 2013, at 3:59 AM, "Mike Audia" wrote:
> Is the error relating to /dev/sr0 relevant to a call to /usr/bin/brtfs? Why
> does it show the superfluous output?
>
> % sudo btrfs fi show /dev/sda3
> failed to open /dev/sr0: No medium found
I get this on Virtual Box VMs, also with parted.
On Sat, 10 Aug 2013 07:07:50 PM Russell Coker wrote:
> I can repeatedly get the following SEGV from running "btrfs device stats" on
> a device node for an Ext3/4 filesystem. This happens with the version of
> the code downloaded from the above GIT repository as well as with an older
> version.
On Sat, 10 Aug 2013 07:19:27 PM Russell Coker wrote:
> But what does generation_errs mean? I'm seeing some on one system.
> Should I be concerned? If I write a Nagios check which ones should be
> warnings and which ones errors?
All I know is that ioctl.h says:
BTRFS_DEV_STAT_GENERATION_ERRS
Hi Linus
Please pull my for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
These are assorted fixes, mostly from Josef nailing down xfstests runs.
Zach also has a long standing fix for problems with readdir wrapping
f_pos (or ctx->pos)
These patches
Is the error relating to /dev/sr0 relevant to a call to /usr/bin/brtfs? Why
does it show the superfluous output?
% sudo btrfs fi show /dev/sda3
failed to open /dev/sr0: No medium found
Label: 'arch64' uuid: ab6f9133-a2ce-4c92-97ab-35cdc3c2d2a9
Total devices 1 FS bytes used 2.46GB
devid 1 s
On Sat, 10 Aug 2013, Chris Samuel wrote:
> On Sun, 4 Aug 2013 03:37:22 PM Bart Noordervliet wrote:
> > a sufficiently up-to-date kernel and btrfs tool will provide the
> > 'btrfs device stats' command, which should give you the info you want.
>
> This is what it looks like:
>
> chris@quad:~/Down
http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git
I can repeatedly get the following SEGV from running "btrfs device stats" on a
device node for an Ext3/4 filesystem. This happens with the version of the
code downloaded from the above GIT repository as well as with an older
versi
12 matches
Mail list logo
