Hard drive hangs after excessive I/O

starts occurring). -- -=[dave]=- Entropy isn't what it used to be. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Hard drive hangs after excessive I/O

installations again. This time I see the IO spurts that I described in my first email; that is, drive thrashes for a while, then hangs for a couple minutes... repeat until host reboot. -- -=[dave]=- Entropy isn't what it used to be. -- To unsubscribe from this list: send the line unsubscribe linux

Re: Hard drive hangs after excessive I/O

in this state that causes IO to periodically hang. -- -=[dave]=- Entropy isn't what it used to be. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

disk-io.c:416: find_and_setup_root: Assertion `!(!root-node)' failed.

A power failure has left me with a broken btrfs. Trying to mount the filesystem with Kernel 3.0 gives me an unrecognized superblock error. btrfs-debug-tree spits out the folowing: parent transid verify failed on 349129785344 wanted 120602 found 120627 parent transid verify failed on

Re: disk-io.c:416: find_and_setup_root: Assertion `!(!root-node)' failed.

OK so on further investigation, I can see that btrfs-debug-tree is failing on: ret = find_and_setup_root(tree_root, fs_info, BTRFS_CSUM_TREE_OBJECTID, csum_root); (line 750 or so) But the same call with extent_root and dev_root as arguments are successful. Would this indicate that some branch on

Re: disk-io.c:416: find_and_setup_root: Assertion `!(!root-node)' failed.

OK so I have recovered all of my data. This was sort of a nerve wrecking experience. I'll share what I've done in case others are experiencing the same problem (I've seen other threads appear complaining of the same assertion which draw no response). So, I filled open_ctree_fd with printf

Re: [RFC] btrfs auto snapshot

* * * * /usr/local/bin/snapshot hourly 6 0 0 * * * /usr/local/bin/snapshot daily 7 0 0 * * 0 /usr/local/bin/snapshot weekly 4 -- -=[dave]=- Entropy isn't what it used to be. pgp09202hq1TV.pgp Description: PGP signature

Re: Applications using fsync cause hangs for several seconds every few minutes

in particular). This behavior goes away after a reboot. I'm running kernel version 3.0. -- -=[dave]=- Entropy isn't what it used to be. pgpGtgOCW3Zae.pgp Description: PGP signature

Re: Honest timeline for btrfsck

in the btrfs ecosystem (lack of fsck being the most frequent reason for not trying btrfs). I know I've got two existing instances that I can test this tool on. -- -=[dave]=- Entropy isn't what it used to be. pgpwZXDAxQRKk.pgp Description: PGP signature

Re: Unable to mount (or, why not to work late at night).

had this happen to me on two occasions. The first time was after a hard reboot. The second was on a totally different machine at a different geographic location, which occurred after nothing more than a reboot. - -- - -=[dave]=- Entropy isn't what it used to be. -BEGIN PGP SIGNATURE

COW a file from snapshot

=always doesn't work (produces the error Invalid cross-device link). Is there a way to recover that file and benefit from COW? - -- - -=[dave]=- Entropy isn't what it used to be. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iF4EAREIAAYFAk7wpKUACgkQXM0u5ajNnCgMUQD/Uf0

Re: Please help me solving BTRFS failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Feb 13, 2012 at 04:58:01PM +0300, Private Inf wrote: Hello Dave, According to this threadhttp://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg11548.htmlyou were able to fix your faulty BTRFS. Looks like I have the same problem

Re: Poll: time to switch skinny-metadata on by default?

-42-g140eccb # btrfstune -x /dev/dm-0 /dev/dm-0 is mounted -- -=[dave]=- Entropy isn't what it used to be. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo

Re: Running out of disk space during BTRFS_IOC_CLONE - rebalance doesn't help

file system [ 201.078328] systemd-journald[213]: Failed to truncate file to its own size: Read-only file system [ 201.088432] systemd-journald[213]: Failed to truncate file to its own size: Read-only file system -- -=[dave]=- Entropy isn't what it used to be. -- To unsubscribe from this list

for-linus and linux 3.8.9

/extent-tree.c Auto-merging fs/btrfs/ctree.c Automatic merge failed; fix conflicts and then commit the result. -- -=[dave]=- Entropy isn't what it used to be. signature.asc Description: This is a digitally signed message part.

Status of raid5/6 in 2014?

the developers are largely silent. Parity based raid would be a powerful addition the the Btrfs feature stack and it's the feature I most anxiously await. Are there any milestones planned for 2014? Keep up the good work... -- -=[dave]=- Entropy isn't what it used to be. -- To unsubscribe from

Re: btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT

. If Btrfs on mdraid isn't an acceptable solution for you, then ZFS is the only responsible alternative. -- -=[dave]=- Entropy isn't what it used to be. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info

Re: [3.14-rc1] BUG: soft lockup - CPU#1 stuck for 22s with 255 GiB BTRFS with only 6 GiB free

code? I had two separate machines that exhibited similar symptoms. Chris's for-linus branch has a fix for this which solved my problems: https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?h=for-linusid=27a377db745ed4d11b3b9b340756857cb8dde07f -- -=[dave]=- Entropy isn't

Clone or Backup Filesystem with compression and dedup

Greetings, I've searched the wiki and the web looking for possible answers to this question and haven't found information that addresses this use case specifically. I would greatly appreciate your help or pointing me in the right direction. Thanks in advance! Dave Use case: I have a 5TB

btrfs open_ctree failed - root fs will not mount

I am running Arch Linux on a system with full disk encryption and the storage is a Samsung 950 Pro NVMe drive (512 GB). The computer is a couple months old. No bad behavior until now. (I'm only using 21 GB of the 512 space on the disk.) btrfs-progs v4.5.1 Today I was using my system normally

Re: send | receive: received snapshot is missing recent files

On Mon, Sep 11, 2017 at 11:19 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 11.09.2017 20:53, Axel Burri пишет: >> On 2017-09-08 06:44, Dave wrote: >>> I'm referring to the link below. Using "btrfs subvolume snapshot -r" >>> copies the Received

Re: ERROR: parent determination failed (btrfs send-receive)

On Mon, Sep 18, 2017 at 12:23 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > > 18.09.2017 05:31, Dave пишет: > > Sometimes when using btrfs send-receive, I get errors like this: > > > > ERROR: parent determination failed for > > > > When this happens

Re: defragmenting best practice?

>On Thu 2017-08-31 (09:05), Ulli Horlacher wrote: >> When I do a >> btrfs filesystem defragment -r /directory >> does it defragment really all files in this directory tree, even if it >> contains subvolumes? >> The man page does not mention subvolumes on this topic. > >No answer so far :-( > >But

Re: defragmenting best practice?

These are great suggestions. I will test several of them (or all of them) and report back with my results once I have done the testing. Thank you! This is a fantastic mailing list. P.S. I'm inclined to stay with Firefox, but I will definitely test Chromium vs Firefox after making a series of

Re: ERROR: parent determination failed (btrfs send-receive)

On Tue, Sep 19, 2017 at 3:37 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 18.09.2017 09:10, Dave пишет: >> I use snap-sync to create and send snapshots. >> >> GitHub - wesbarnett/snap-sync: Use snapper snapshots to backup to external >> drive >>

Re: ERROR: parent determination failed (btrfs send-receive)

On Mon, Sep 18, 2017 at 12:23 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 18.09.2017 05:31, Dave пишет: >> Sometimes when using btrfs send-receive, I get errors like this: >> >> ERROR: parent determination failed for >> >> When this happens, b

ERROR: parent determination failed (btrfs send-receive)

Sometimes when using btrfs send-receive, I get errors like this: ERROR: parent determination failed for When this happens, btrfs send-receive backups fail. And all subsequent backups fail too. The issue seems to stem from the fact that an automated cleanup process removes certain earlier

Re: snapshots of encrypted directories?

On Fri, Sep 15, 2017 at 6:01 AM, Ulli Horlacher wrote: > > On Fri 2017-09-15 (06:45), Andrei Borzenkov wrote: > > > The actual question is - do you need to mount each individual btrfs > > subvolume when using encfs? > > And even worse it goes with ecryptfs: I do not

difference between -c and -p for send-receive?

new subject for new question On Mon, Sep 18, 2017 at 1:37 PM, Andrei Borzenkov wrote: > >> What scenarios can lead to "ERROR: parent determination failed"? > > > > The man page for btrfs-send is reasonably clear on the requirements > > btrfs imposes. If you want to use

Re: send | receive: received snapshot is missing recent files

gt; The problem can be that you have a Received UUID on the source volume. This > breaks send-receive. > > From: Dave <davestechs...@gmail.com> -- Sent: 2017-09-07 - 06:43 > >> Here is more info and a possible (shocking) explanation. This >> aggregates my prio

send | receive: received snapshot is missing recent files

I'm running Arch Linux on BTRFS. I use Snapper to take hourly snapshots and it works without any issues. I have a bash script that uses send | receive to transfer snapshots to a couple external HDD's. The script runs daily on a systemd timer. I set all this up recently and I first noticed that it

Re: send | receive: received snapshot is missing recent files

l. Thanks for any further feedback, including answers to my questions and comments about whether this is a known issue. On Thu, Sep 7, 2017 at 8:39 AM, Dave <davestechs...@gmail.com> wrote: > > Hello. Can anyone further explain this issue ("you have a Received UUID on > the

Re: send | receive: received snapshot is missing recent files

recent files are MISSING Any ideas what could be causing this problem with incremental backups? On Wed, Sep 6, 2017 at 3:23 PM, Dave <davestechs...@gmail.com> wrote: > > Here is more info on this problem. I can reproduce this without using my > script. Simple btrfs commands

Re: send | receive: received snapshot is missing recent files

olume read-write, I > recommend to use "btrfs subvolume snapshot ". > > There is a FAQ entry on btrbk on how to fix this: > > https://github.com/digint/btrbk/blob/master/doc/FAQ.md#im-getting-an-error-aborted-received-uuid-is-set > > > On 2017-09-07 15:34, Dave wrote: > >

Re: send | receive: received snapshot is missing recent files

Here is more info and a possible (shocking) explanation. This aggregates my prior messages and it provides an almost complete set of steps to reproduce this problem. Linux srv 4.9.41-1-lts #1 SMP Mon Aug 7 17:32:35 CEST 2017 x86_64 GNU/Linux btrfs-progs v4.12 My steps: [root@srv]# sync

Re: Need help with incremental backup strategy (snapshots, defragmentingt & performance)

On Tue, Nov 14, 2017 at 3:50 AM, Roman Mamedov <r...@romanrm.net> wrote: > > On Mon, 13 Nov 2017 22:39:44 -0500 > Dave <davestechs...@gmail.com> wrote: > > > I have my live system on one block device and a backup snapshot of it > > on another block device. I

Re: Need help with incremental backup strategy (snapshots, defragmentingt & performance)

On Wed, Nov 1, 2017 at 1:15 AM, Roman Mamedov <r...@romanrm.net> wrote: > On Wed, 1 Nov 2017 01:00:08 -0400 > Dave <davestechs...@gmail.com> wrote: > >> To reconcile those conflicting goals, the only idea I have come up >> with so far is to use btrfs send-receive

Re: Need help with incremental backup strategy (snapshots, defragmentingt & performance)

On Wed, Nov 1, 2017 at 4:34 AM, Marat Khalili wrote: >> We do experience severe performance problems now, especially with >> Firefox. Part of my experiment is to reduce the number of snapshots on >> the live volumes, hence this question. > > Just for statistics, how many snapshots

Re: defragmenting best practice?

On Wed, Nov 1, 2017 at 9:31 AM, Duncan <1i5t5.dun...@cox.net> wrote: > Dave posted on Tue, 31 Oct 2017 17:47:54 -0400 as excerpted: > >> 6. Make sure Firefox is running in multi-process mode. (Duncan's >> instructions, while greatly appreciated and very useful, left me &g

Re: defragmenting best practice?

On Wed, Nov 1, 2017 at 1:48 PM, Peter Grandi wrote: >> When defragmenting individual files on a BTRFS filesystem with >> COW, I assume reflinks between that file and all snapshots are >> broken. So if there are 30 snapshots on that volume, that one >> file will suddenly

Re: Need help with incremental backup strategy (snapshots, defragmentingt & performance)

On Wed, Nov 1, 2017 at 2:19 AM, Marat Khalili wrote: > You seem to have two tasks: (1) same-volume snapshots (I would not call them > backups) and (2) updating some backup volume (preferably on a different > box). By solving them separately you can avoid some complexity... Yes, it

Re: defragmenting best practice?

On Thu, Nov 2, 2017 at 7:17 AM, Austin S. Hemmelgarn wrote: >> And the worst performing machine was the one with the most RAM and a >> fast NVMe drive and top of the line hardware. > > Somewhat nonsensically, I'll bet that NVMe is a contributing factor in this > particular

Re: defragmenting best practice?

On Wed, Nov 1, 2017 at 8:21 AM, Austin S. Hemmelgarn wrote: >> The cache is in a separate location from the profiles, as I'm sure you >> know. The reason I suggested a separate BTRFS subvolume for >> $HOME/.cache is that this will prevent the cache files for all >>

Parity-based redundancy (RAID5/6/triple parity and beyond) on BTRFS and MDADM (Dec 2014) – Ronny Egners Blog

Has this been discussed here? Has anything changed since it was written? Parity-based redundancy (RAID5/6/triple parity and beyond) on BTRFS and MDADM (Dec 2014) – Ronny Egners Blog

Re: defragmenting best practice?

On Thu, Nov 2, 2017 at 7:07 AM, Austin S. Hemmelgarn <ahferro...@gmail.com> wrote: > On 2017-11-01 21:39, Dave wrote: >> I'm going to make this change now. What would be a good way to >> implement this so that the change applies to the $HOME/.cache of each >> user?

Re: defragmenting best practice?

On Thu, Nov 2, 2017 at 5:16 PM, Kai Krakow wrote: > > You may want to try btrfs autodefrag mount option and see if it > improves things (tho, the effect may take days or weeks to apply if you > didn't enable it right from the creation of the filesystem). > > Also,

Re: Problem with file system

On Sat, Nov 4, 2017 at 1:25 PM, Chris Murphy <li...@colorremedies.com> wrote: > > On Sat, Nov 4, 2017 at 1:26 AM, Dave <davestechs...@gmail.com> wrote: > > On Mon, Oct 30, 2017 at 5:37 PM, Chris Murphy <li...@colorremedies.com> > > wrote: > >> > &g

Re: Need help with incremental backup strategy (snapshots, defragmentingt & performance)

On Thu, Nov 2, 2017 at 4:46 PM, Kai Krakow <hurikha...@gmail.com> wrote: > Am Wed, 1 Nov 2017 02:51:58 -0400 > schrieb Dave <davestechs...@gmail.com>: > >> > >> >> To reconcile those conflicting goals, the only idea I have come up >> >&g

Re: Problem with file system

On Mon, Oct 30, 2017 at 5:37 PM, Chris Murphy wrote: > > That is not a general purpose file system. It's a file system for admins who > understand where the bodies are buried. I'm not sure I understand your comment... Are you saying BTRFS is not a general purpose file

Re: defragmenting best practice?

On Tue, Oct 31, 2017 someone wrote: > > > > 2. Put $HOME/.cache on a separate BTRFS subvolume that is mounted > > nocow -- it will NOT be snapshotted I did exactly this. It servers the purpose of avoiding snapshots. However, today I saw the following at https://wiki.archlinux.org/index.php/Btrfs

Re: Problem with file system

This is a very helpful thread. I want to share an interesting related story. We have a machine with 4 btrfs volumes and 4 Snapper configs. I recently discovered that Snapper timeline cleanup been turned off for 3 of those volumes. In the Snapper configs I found this setting:

Re: defragmenting best practice?

many unexpected changes when using sync, so we do not use it. On Thu, Sep 21, 2017 at 7:09 AM, Duncan <1i5t5.dun...@cox.net> wrote: > Dave posted on Wed, 20 Sep 2017 02:38:13 -0400 as excerpted: > >> Here's my scenario. Some months ago I built an over-the-top powerful >>

Re: defragmenting best practice?

On Tue, Oct 31, 2017 at 7:06 PM, Peter Grandi wrote: > > Also nothing forces you to defragment a whole filesystem, you > can just defragment individual files or directories by using > 'find' with it. Thanks for that info. When defragmenting individual files on a

Re: Need help with incremental backup strategy (snapshots, defragmentingt & performance)

On Wed, Nov 1, 2017 at 1:15 AM, Roman Mamedov <r...@romanrm.net> wrote: > On Wed, 1 Nov 2017 01:00:08 -0400 > Dave <davestechs...@gmail.com> wrote: > >> To reconcile those conflicting goals, the only idea I have come up >> with so far is to use btrfs send-receive

Need help with incremental backup strategy (snapshots, defragmentingt & performance)

Our use case requires snapshots. btrfs snapshots are best solution we have found for our requirements, and over the last year snapshots have proven their value to us. (For this discussion I am considering both the "root" volume and the "home" volume on a typical desktop workstation. Also, all

how to make a cache directory nodatacow while also excluded from snapshots?

I want to exclude my ~/.cache directory from snapshots. The obvious way to do this is to mount a btrfs subvolume at that location. However, I also want the ~/.cache directory to be nodatacow. Since the parent volume is COW, I believe it isn't possible to mount the subvolume with different mount

btrfs send | receive ERROR rename file exists

Can anyone give me any ideas why this error would happen? The receive directory started empty. Snapshot 3 exists at both source and target. # mkdir /.snapshots/bw538/ # btrfs send -p /mnt/backup/root/laptop/3/snapshot/ /mnt/backup/root/laptop/4/snapshot/ | btrfs receive /.snapshots/bw538/ At

a new kind of "No space left on device" error

This is one I have not seen before. When running a simple, well-tested and well-used script that makes backups using btrfs send | receive, I got these two errors: At subvol snapshot ERROR: rename o131621-1091-0 -> usr/lib/node_modules/node-gyp/gyp/pylib/gyp/MSVSVersion.py failed: No space left

btrfs-qgroup-rescan using 100% CPU

I'm using btrfs and snapper on a system with an SSD. On this system when I run `snapper -c root ls` (where `root` is the snapper config for /), the process takes a very long time and top shows the following process using 100% of the CPU: kworker/u8:6+btrfs-qgroup-rescan I have multiple

Re: [RFC v0 0/4] sys_copy_range() rough draft

as efficiently as possible? Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [RFC v0 0/4] sys_copy_range() rough draft

On Tue, May 14, 2013 at 03:04:40PM -0700, Zach Brown wrote: On Wed, May 15, 2013 at 07:42:51AM +1000, Dave Chinner wrote: On Tue, May 14, 2013 at 02:15:22PM -0700, Zach Brown wrote: I'm going to keep hacking away at this. My next step is to get ext4 supporting .copy_range, probably

Re: [PATCH] xfstests: btrfs 308: regression test for btrfs send

to $seqres.full, so if the test fails there's debug output to look at... Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org

Re: [PATCH] xfstests: btrfs/308: simple sparse copy testcase for btrfs

monatomically increasing numbers for the tests anymore in the fileystem specifc test directories - you could make these tests btrfs/00[1-4] :) Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message

Re: [PATCH] xfstests btrfs/314: test send / receive

... Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[3.10-rc6] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]()

Hit this while running this script in a loop.. https://github.com/kernelslacker/io-tests/blob/master/setup.sh [34385.251507] [ cut here ] [34385.254068] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]() [34385.257275] Modules linked in:

Re: [3.10-rc6] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]()

On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote: Quoting Dave Jones (2013-06-17 14:20:06) On Mon, Jun 17, 2013 at 01:39:42PM -0400, Chris Mason wrote: Quoting Dave Jones (2013-06-17 09:49:55) Hit this while running this script in a loop.. https://github.com

btrfs triggered 'MAX_LOCKDEP_CHAINS too low'

Dave -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [3.10-rc6] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]()

On Wed, Jun 19, 2013 at 02:02:33PM -0400, Chris Mason wrote: Quoting Dave Jones (2013-06-17 14:58:10) On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote: Quoting Dave Jones (2013-06-17 14:20:06) On Mon, Jun 17, 2013 at 01:39:42PM -0400, Chris Mason wrote: Quoting

btrfs triggered lockdep WARN.

? We're most confused. 707 */ 708 WARN_ON_ONCE(class-name != lock-name); Most confusing indeed. Dave -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More

Re: btrfs triggered lockdep WARN.

On Thu, Jun 27, 2013 at 11:01:30AM -0400, Chris Mason wrote: Quoting Dave Jones (2013-06-27 10:58:24) Another bug caused by this script. https://github.com/kernelslacker/io-tests/blob/master/setup.sh I'm still struggling to reproduce that one here. I've tried every variation I can

Re: btrfs triggered lockdep WARN.

. Ok, could you please try this with some heavy memory pressure? I'm hoping to trigger a use-after-free that points us in the right direction. Have anything in particular in mind ? I tried a make -j on a kernel tree in a loop, but nothing new is shaking out. Dave -- To unsubscribe

Re: [PATCH] btrfs: fix file truncation if FALLOC_FL_KEEP_SIZE is specified

other file systems can be made to be consistent, and I'd like to make sure we all agree what is the correct behavior before we wander down that road. Thanks, I couldn't have said it better myself. Jeff, can you take care of this, please? Cheers, Dave. -- Dave Chinner da...@fromorbit.com

Re: [PATCH v3] xfstests: btrfs/316: cross-subvolume sparse copy

from Eric: http://oss.sgi.com/archives/xfs/2013-03/msg00231.html Two new common/rc functions used in this script (_require_cp_reflink and _verify_reflink) have been submitted recently: http://oss.sgi.com/archives/xfs/2013-05/msg00745.html Thanks to Eric Sandeen and Dave Chinner

Re: [PATCH v3] xfstests: btrfs/316: cross-subvolume sparse copy

On Tue, Jul 02, 2013 at 11:51:21AM -0400, Eric Sandeen wrote: On Jul 2, 2013, at 10:28 AM, Koen De Wit koen.de@oracle.com wrote: Dave, Thanks for the review. I will clean up the commit message and do a full mail-to-myself-and-test-patch round trip to avoid errors like the wrong

Re: [PATCH v3] xfstests: btrfs/316: cross-subvolume sparse copy

On Wed, Jul 03, 2013 at 12:02:52PM +0200, Koen De Wit wrote: On 07/03/2013 08:37 AM, Dave Chinner wrote: On Tue, Jul 02, 2013 at 11:51:21AM -0400, Eric Sandeen wrote: On Jul 2, 2013, at 10:28 AM, Koen De Wit koen.de@oracle.com wrote: Dave, Thanks for the review. I will clean

Re: [PATCH 0/2] introduce list_for_each_entry_del

to this? There are many loops that actually require list_del_init() rather than list_del()... Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http

Need help mounting broken btrfs Fedora 19

I need some help as may have lost some number of files on a btrfs raid 1 volume. I'm not quite sure what happend which, I know, only adds to the problem. On my computer #1 I had only a month or so ago installed Fedora 19 Beta and at the time of install chose BTRFS, raid 1. Recently one of the

Re: Need help mounting broken btrfs Fedora 19

Thanks for your reply. I have tried -o degraded and recover but I keep getting the error messages above in dmesg such as: btrfs: failed to read chunk root on sdc2 On Sun, Jul 14, 2013 at 1:49 PM, Hugo Mills h...@carfax.org.uk wrote: On Sun, Jul 14, 2013 at 01:43:41PM +, Dave Barnum wrote

Re: Need help mounting broken btrfs Fedora 19

Thanks Wang, This was the result: root@ubuntu:/downloads/btrfs-progs# ./btrfs chunk-recover /dev/sdc2 no recoverable chunk Recover the chunk tree successfully. Still unable to mount. On Sun, Jul 14, 2013 at 2:03 PM, Wang Shilong wangshilong1...@gmail.com wrote: Hello, You call pull from:

[PATCH V8 25/33] btrfs: add support for read_iter and write_iter

btrfs can use generic_file_read_iter(). Base btrfs_file_write_iter() on btrfs_file_aio_write(), then have the latter call the former. Signed-off-by: Dave Kleikamp dave.kleik...@oracle.com Cc: Zach Brown z...@zabbo.net Cc: Chris Mason chris.ma...@fusionio.com Cc: linux-btrfs@vger.kernel.org

Fix leak in __btrfs_map_block error path

If we bail out when the stripe alloc fails, we need to undo the earlier allocation of raid_map. Signed-off-by: Dave Jones da...@redhat.com diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c index 78b8717..6a0f52f 100644 --- a/fs/btrfs/volumes.c +++ b/fs/btrfs/volumes.c @@ -4671,6 +4671,7

Re: [PATCH v3 1/2] xfstests: add fssum tool

? Please, let's keep crypto out of xfstests if we can. That's just going to add a nightmare of US export compliance garbage to any distro that wants to package and ship this Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs

Re: [PATCH] xfstests: fix device lookup in btrfs/003

...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org

Re: [PATCH] xfstests: introduce _filter_backtick

needed to set LC_ALL=C so that it didn't use weird UTF-8 encodings for the quotes instead of a simple backtick. Full patch below. Cheers, Dave. -- Dave Chinner da...@fromorbit.com xfstests: unify apostrophes in output files From: Tomas Racek tra...@redhat.com With coreutils v8.16 the style

Re: Notes on support for multiple devices for a single filesystem

On Wed, 2008-12-17 at 15:04 -0700, Andreas Dilger wrote: On Dec 17, 2008 08:23 -0500, Christoph Hellwig wrote: An alternative way, supported by optionally by ext3 and reiserfs and exclusively supported by jfs is to open the journal device by the device number (dev_t) of the block special

Re: [PATCH -v5][RFC]: mutex: implement adaptive spinning

On Wed, 2009-01-07 at 13:58 -0800, Linus Torvalds wrote: On Wed, 7 Jan 2009, Peter Zijlstra wrote: Do we really have to re-do all that code every loop? No, you're right, we can just look up the cpu once. Which makes Andrew's argument that probe_kernel_address() isn't in any hot path

Re: Warning and BUG with btrfs and corrupted image

, swap, iso9660, ext2, ext3, ext4, minix, bfs, befs, hfs, hfs+, qnx4, affs and cramfs on each of my two test machines. Any reason you are not testing XFS in that set? Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs

Re: Warning and BUG with btrfs and corrupted image

On Tue, Jan 20, 2009 at 11:20:19PM +0100, Pavel Machek wrote: On Tue 2009-01-20 08:28:29, Christoph Hellwig wrote: On Tue, Jan 20, 2009 at 11:59:44PM +1100, Dave Chinner wrote: So far the responses from xfs folks have been disappointing, if you are interested in bugreports i can send

Re: Warning and BUG with btrfs and corrupted image

On Mon, Jan 26, 2009 at 05:27:11PM +0100, Pavel Machek wrote: On Wed 2009-01-21 15:00:42, Dave Chinner wrote: On Tue, Jan 20, 2009 at 11:20:19PM +0100, Pavel Machek wrote: On Tue 2009-01-20 08:28:29, Christoph Hellwig wrote: I think that was the issue with the debug builds. If you do

Re: Warning and BUG with btrfs and corrupted image

On Wed, Feb 04, 2009 at 07:29:51PM +0100, Pavel Machek wrote: On Sun 2009-02-01 12:40:50, Dave Chinner wrote: On Mon, Jan 26, 2009 at 05:27:11PM +0100, Pavel Machek wrote: On Wed 2009-01-21 15:00:42, Dave Chinner wrote: + Turning this option on will result in kernel panicking any time

Re: [Jfs-discussion] benchmark results

these benchmarks run on each filesystem for each kernel release so ext/xfs/btrfs all get some regular basic performance regression test coverage? Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message

[PATCH] fix return value when mount fail

as -EINVAL Signed-off-by: Dave Young hidave.darks...@gmail.com --- fs/btrfs/disk-io.c |4 +++- fs/btrfs/volumes.c |8 +--- 2 files changed, 8 insertions(+), 4 deletions(-) --- linux-2.6.orig/fs/btrfs/disk-io.c 2010-12-29 21:53:17.47338 +0800 +++ linux-2.6/fs/btrfs/disk-io.c

[PATCH retry] btrfs: mount failure return value fix

Here fix the return value as -EINVAL Signed-off-by: Dave Young hidave.darks...@gmail.com --- fs/btrfs/disk-io.c |4 +++- fs/btrfs/volumes.c |8 +--- 2 files changed, 8 insertions(+), 4 deletions(-) --- linux-2.6.orig/fs/btrfs/disk-io.c 2010-12-29 21:53:17.47338 +0800 +++ linux

Re: [PATCH 1/6] fs: add hole punching to fallocate

should feel obliged to implement. It could, but it still needs better justification. Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http

Re: [PATCH 1/6] fs: add hole punching to fallocate

On Tue, Jan 11, 2011 at 04:13:42PM -0500, Lawrence Greenfield wrote: On Tue, Nov 9, 2010 at 6:40 PM, Dave Chinner da...@fromorbit.com wrote: The historical reason for such behaviour existing in XFS was that in 1997 the CPU and IO latency cost of unwritten extent conversion was significant

Re: [PATCH v2] Check for immutable flag in fallocate path

, not in every filesystem. The same checks have to be made for every filesystem, so they should be done before calling out the filesystems regardless of what functionality the filesystem actually supports. Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line

Re: [PATCH 1/2 v2] fs: add SEEK_HOLE and SEEK_DATA flags

On 05/04/2011 02:10 PM, Josef Bacik wrote: On 05/04/2011 03:04 PM, valdis.kletni...@vt.edu wrote: On Wed, 04 May 2011 13:58:39 EDT, Josef Bacik said: -SEEK_HOLE: this moves the file pos to the nearest hole in the file from the given position. Nearest, or next? Solaris defines it as next,

Re: [PATCH 1/2 v2] fs: add SEEK_HOLE and SEEK_DATA flags

On 05/04/2011 04:54 PM, Dave Kleikamp wrote: The comments in fs.h say closest. You may want to change them to next as well. Sorry. Missed some of the replies before I responded. Already addressed. Shaggy -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body

Re: [PATCH 1/2] fs: add a DCACHE_NEED_LOOKUP flag for d_flags

dentries. That way the sb generating them all would self-limit without greatly affecting the working set of dentries on other filesystems... Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord

[BUG 3.0-rc1] oops during file removal, severe lock contention

, performance on this create workload my test box is roughly 45k creates/s for btrfs, 75k creates/s for ext4 and 110k create/s for XFS. btrfs is without doubt being slowed down by the lock contention problems Cheers, Dave. -- Dave Chinner da...@fromorbit.com -- To unsubscribe from this list: send

  1   2   3   4   5   6   7   >