Before the patch, we passed wrong value to _require_fs_space, which
should be in unit of 1024, but passed in unit of GB.
Fix it and add better prompt for falloc failure.
Signed-off-by: Qu Wenruo
---
tests/btrfs/079 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tests/b
Hi Anand,
Precondition : Previous filesystem on eMMC was --- ext4
Use case : Now format eMMC to btrfs format, using ---mkfs.btrfs---
mkfs.btrfs denies formatting eMMC telling that eMMC contain an existing
filesystem(ext4).
In my opinion mkfs.btrfs must allow to format eMMC with btrfs even i
On 12/26/2014 11:24 PM, Ankur Tank wrote:
Hi,
I wanted to test btrfs on the eMMC of beaglebone black based custom board.
Precondition: eMMC is formatted with ext4 filesystem
Use case:
Format eMMC with mkfs.btrfs -L
Result:
Mkfs.btrfs denies formatting eMMC because its ex
Martin Steigerwald posted on Sun, 28 Dec 2014 17:58:17 +0100 as excerpted:
> The fstrim on /home returns immediately. It does not even seem to trim
> anything. What could be the cause for that?
While I don't know your mapper layout, trim working on the others but not
on /home sounds to me like e
On Sat, Dec 27, 2014 at 08:23:59PM +0100, Martin Steigerwald wrote:
> My simple test case didn´t trigger it, and I so not have another twice 160
> GiB available on this SSDs available to try with a copy of my home
> filesystem. Then I could safely test without bringing the desktop session to
> an h
On 12/28/2014 08:58 AM, Martin Steigerwald wrote:
Hi!
After my recent tests with my /home filesystem and the up and downsizing of
it I get:
merkaba:~> LANG=C fstrim -v /home
/home: 0 B (0 bytes) trimmed
merkaba:~> LANG=C fstrim -v /
/: 24.5 GiB (26257555456 bytes) trimmed
merkaba:~> LANG=C fst
On 12/28/2014 07:42 AM, Martin Steigerwald wrote:
Am Sonntag, 28. Dezember 2014, 06:52:41 schrieb Robert White:
On 12/28/2014 04:07 AM, Martin Steigerwald wrote:
Am Samstag, 27. Dezember 2014, 20:03:09 schrieb Robert White:
Now:
The complaining party has verified the minimum, repeatable case
On Mon, Dec 29, 2014 at 01:00:47AM +0500, Roman Mamedov wrote:
> > Will btrfs scrub, even if it takes about 24H to run for me, tell me
> > which FS is affected and if so do I run btrfs repair?
>
> I had this: http://www.spinics.net/lists/linux-btrfs/msg40586.html
>
> 1) I determined which btrfs o
On Sun, 28 Dec 2014 11:26:14 -0800
Marc MERLIN wrote:
> Not sure if it's useful to anyone, but there you go. This happened after a
> forced
> power cycle:
>
> BTRFS info (device dm-1): disk space caching is enabled
> [ cut here ]
> WARNING: CPU: 2 PID: 778 at fs/btrfs/de
Not sure if it's useful to anyone, but there you go. This happened after a
forced
power cycle:
BTRFS info (device dm-1): disk space caching is enabled
[ cut here ]
WARNING: CPU: 2 PID: 778 at fs/btrfs/delayed-inode.c:1410
btrfs_assert_delayed_root_empty+0x32/0x34()
Module
On 28 December 2014 at 13:03, Martin Steigerwald wrote:
>
> BTW, I found that the Oracle blog didn´t work at all for me. I completed
> a cycle of defrag, sdelete -c and VBoxManage compact, [...] and it
> apparently did *nothing* to reduce the size of the file.
They've changed the argument to -z;
Hi!
After my recent tests with my /home filesystem and the up and downsizing of
it I get:
merkaba:~> LANG=C fstrim -v /home
/home: 0 B (0 bytes) trimmed
merkaba:~> LANG=C fstrim -v /
/: 24.5 GiB (26257555456 bytes) trimmed
merkaba:~> LANG=C fstrim -v /daten
/daten: 2.8 GiB (3016101888 bytes)
Am Sonntag, 28. Dezember 2014, 16:42:20 schrieb Martin Steigerwald:
> Am Sonntag, 28. Dezember 2014, 06:52:41 schrieb Robert White:
> > On 12/28/2014 04:07 AM, Martin Steigerwald wrote:
> > > Am Samstag, 27. Dezember 2014, 20:03:09 schrieb Robert White:
> > >> Now:
> > >>
> > >> The complaining par
Am Sonntag, 28. Dezember 2014, 06:52:41 schrieb Robert White:
> On 12/28/2014 04:07 AM, Martin Steigerwald wrote:
> > Am Samstag, 27. Dezember 2014, 20:03:09 schrieb Robert White:
> >> Now:
> >>
> >> The complaining party has verified the minimum, repeatable case of
> >> simple file allocation on a
Am Sonntag, 28. Dezember 2014, 14:56:21 schrieb Martin Steigerwald:
> Am Sonntag, 28. Dezember 2014, 14:40:32 schrieb Martin Steigerwald:
> > Am Sonntag, 28. Dezember 2014, 14:00:19 schrieb Martin Steigerwald:
> > > Am Samstag, 27. Dezember 2014, 14:55:58 schrieb Martin Steigerwald:
> > > > Summari
On 12/28/2014 04:07 AM, Martin Steigerwald wrote:
Am Samstag, 27. Dezember 2014, 20:03:09 schrieb Robert White:
Now:
The complaining party has verified the minimum, repeatable case of
simple file allocation on a very fragmented system and the responding
party and several others have understood
Am Sonntag, 28. Dezember 2014, 14:40:32 schrieb Martin Steigerwald:
> Am Sonntag, 28. Dezember 2014, 14:00:19 schrieb Martin Steigerwald:
> > Am Samstag, 27. Dezember 2014, 14:55:58 schrieb Martin Steigerwald:
> > > Summarized at
> > >
> > > Bug 90401 - btrfs kworker thread uses up 100% of a Sandy
Am Sonntag, 28. Dezember 2014, 14:00:19 schrieb Martin Steigerwald:
> Am Samstag, 27. Dezember 2014, 14:55:58 schrieb Martin Steigerwald:
> > Summarized at
> >
> > Bug 90401 - btrfs kworker thread uses up 100% of a Sandybridge core for
> > minutes on random write into big file
> > https://bugzill
Am Samstag, 27. Dezember 2014, 14:55:58 schrieb Martin Steigerwald:
> Summarized at
>
> Bug 90401 - btrfs kworker thread uses up 100% of a Sandybridge core for
> minutes on random write into big file
> https://bugzilla.kernel.org/show_bug.cgi?id=90401
>
> see below. This is reproducable with fio
Am Samstag, 27. Dezember 2014, 20:03:09 schrieb Robert White:
> Now:
>
> The complaining party has verified the minimum, repeatable case of
> simple file allocation on a very fragmented system and the responding
> party and several others have understood and supported the bug.
I didn´t yet prov
Am Samstag, 27. Dezember 2014, 20:03:09 schrieb Robert White:
> On 12/27/2014 05:01 PM, Bardur Arantsson wrote:
> > On 2014-12-28 01:25, Robert White wrote:
> >> On 12/27/2014 08:01 AM, Martin Steigerwald wrote:
> From how you write I get the impression that you think everyone else
> >>> besi
Am Samstag, 27. Dezember 2014, 16:06:13 schrieb Robert White:
> >
> >> I also don't know what kind of tool you are using, but it might be
> >> repeatedly trying and failing to fallocate the file as a single
> >> extent or something equally dumb.
> >
> > Userspace doesn't as far as I know, get t
22 matches
Mail list logo
