From: Filipe Manana
Test that if we truncate a file to reduce its size, rename it and then
fsync it, after a power failure the file has a correct size and name.
This test is motivated by a bug found in btrfs, which is fixed by a
patch for the linux kernel titled:
"Btrfs: fix incorrect file si
On Tue, Mar 5, 2019 at 5:59 AM Amir Goldstein wrote:
>
> On Tue, Mar 5, 2019 at 12:31 AM Filipe Manana wrote:
> >
> > On Mon, Mar 4, 2019 at 5:59 PM Amir Goldstein wrote:
> > >
> > > On Mon, Mar 4, 2019 at 5:23 PM Filipe Manana wrote:
> > > >
> > > > On Mon, Mar 4, 2019 at 3:04 PM Amir Goldstei
> > As I wrote to Dave, if file is not "metadata dirty" before rename,
> > then whether or not rename dirties to file for fsync is a filesystem
> > specific implementation detail that is not in any standard.
> >
> > Since filesystems tend to try to optimize out unneeded journal
> > commits, so the
On Thu, Feb 28, 2019 at 10:22:06AM +0800, Qu Wenruo wrote:
> A lot of editor/IDE related config files are dotfiles, like .vimrc
> or .clang_complete.
>
> Instead of adding gitignore entry for each editor/IDE, just ignore all
> dotfiles.
Fortunatelly it still works for tracked dotfiles like .travi
On 2019/3/5 下午8:27, David Sterba wrote:
> On Thu, Feb 28, 2019 at 10:22:06AM +0800, Qu Wenruo wrote:
>> A lot of editor/IDE related config files are dotfiles, like .vimrc
>> or .clang_complete.
>>
>> Instead of adding gitignore entry for each editor/IDE, just ignore all
>> dotfiles.
>
> Fortunat
On Wed, Feb 20, 2019 at 09:16:04AM +, Steven Davies wrote:
> Provide an option in `btrfs receive` to suppress the informational
> messages when writing files.
Thank, looks ok to me, the 'receive' command already has the verbosity
option so it makes sense to have both.
> Signed-off-by: Steven
On Mon, Feb 25, 2019 at 07:16:43PM +0100, Adam Borowski wrote:
> The code fails if the third section is missing (like "4.18") or is followed
> by anything but "." or "-". This happens for example if we're not exactly
> at a tag and CONFIG_LOCALVERSION_AUTO=n (which results in "4.18.5+").
>
> Sign
On Mon, Feb 25, 2019 at 07:16:44PM +0100, Adam Borowski wrote:
> Defragging an executable conflicts both way with it being run, resulting in
> ETXTBSY. This either makes defrag fail or prevents the program from being
> executed.
>
> Kernels 4.19-rc1 and later allow defragging files you could have
On Tue, Mar 05, 2019 at 08:35:39PM +0800, Qu Wenruo wrote:
>
>
> On 2019/3/5 下午8:27, David Sterba wrote:
> > On Thu, Feb 28, 2019 at 10:22:06AM +0800, Qu Wenruo wrote:
> >> A lot of editor/IDE related config files are dotfiles, like .vimrc
> >> or .clang_complete.
> >>
> >> Instead of adding giti
On Fri, Sep 14, 2018 at 03:49:44PM +0800, Qu Wenruo wrote:
> In github issues, one user reports unexpected ENOSPC error if enabling
> datasum.
> After some investigation, it looks like that during ext2_saved/image
> creation, we could create large file extent whose size can be 128M (max
> data exte
On Fri, Jun 01, 2018 at 04:27:46PM +0800, Qu Wenruo wrote:
> Reuse extent-cache facility to record multiple bytenr so '-b|--block'
> can be specified multiple times.
>
> Despite that, add a sector size alignment check before we try to print a
> tree block.
> (Please note that, nodesize alignment c
On Tue, Mar 05, 2019 at 07:39:28AM +0200, Amir Goldstein wrote:
> On Tue, Mar 5, 2019 at 2:50 AM Dave Chinner wrote:
> >
> > On Mon, Mar 04, 2019 at 05:04:23PM +0200, Amir Goldstein wrote:
> > > On Mon, Mar 4, 2019 at 4:44 PM wrote:
> > > >
> > > > From: Filipe Manana
> > > >
> > > > Test that i
[BUG]
For the new multiple -b parameter supporting, we could hit this bug on a
16K node sized btrfs:
$ ./btrfs inspect dump-tree -b 1024 -b 2048 -b 4096 -b 8192 zimg
btrfs-progs v4.20.2
ERROR: tree block bytenr 1024 is not aligned to sectorsize 4096
ERROR: tree block bytenr 2048 is not alig
This patch adds a new sys fs interface, 'profiler', for user to get
real time performance data.
The content of /sys/fs/btrfs//profiler is generated at the time of
read, so user could have full control of the duration resolution.
The output example would be:
timestamp = 16364075995092ns
duration =
This patch introduce the skeleton of btrfs performance profiler.
The objective of btrfs performance profiler is to provide various
indicator to locate possible performance bottleneck.
Initial btrfs profiler only supports sleepable tree lock anaylyse for
the following trees:
- fs/subvolume trees
-
For btrfs tree locking, there are only 2 functions can sleep:
- btrfs_tree_read_lock()
It will wait for any blocking writers
- btrfs_tree_lock()
It will wait for any blocking readers or writers
Other functions only depends on rwlock which won't sleep.
We doesn't really care about the spinning
This patchset can be fetched from github:
https://github.com/adam900710/linux/tree/perf_tree_lock
Which is based on v5.0-rc7 tag.
Although we have ftrace/perf to do various performance analyse, under most
case the granularity is too small, resulting data flood for users.
This RFC patchset provide
On Wed, Mar 6, 2019 at 12:33 AM Dave Chinner wrote:
>
> On Tue, Mar 05, 2019 at 07:39:28AM +0200, Amir Goldstein wrote:
> > On Tue, Mar 5, 2019 at 2:50 AM Dave Chinner wrote:
> > >
> > > On Mon, Mar 04, 2019 at 05:04:23PM +0200, Amir Goldstein wrote:
> > > > On Mon, Mar 4, 2019 at 4:44 PM wrote:
18 matches
Mail list logo
