Re: Please add more info to dmesg output on I/O error

2017-03-02 3:40 GMT+03:00 Chris Murphy : > On Wed, Mar 1, 2017 at 12:38 PM, Kai Krakow wrote: >> Am Wed, 1 Mar 2017 19:04:26 +0300 >> schrieb Timofey Titovets : >> >>> Hi, today i try move my FS from old HDD to new SSD >>> While

Re: Please add more info to dmesg output on I/O error

On Wed, Mar 1, 2017 at 12:38 PM, Kai Krakow wrote: > Am Wed, 1 Mar 2017 19:04:26 +0300 > schrieb Timofey Titovets : > >> Hi, today i try move my FS from old HDD to new SSD >> While processing i catch I/O error and device remove operation was >> canceled

Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists

At 02/02/2017 08:01 PM, Marc Joliet wrote: On Sunday 28 August 2016 15:29:08 Kai Krakow wrote: Hello list! Hi list [kernel message snipped] Btrfs --repair refused to repair the filesystem telling me something about compressed extents and an unsupported case, wanting me to take an image

raid1 degraded mount still produce single chunks, writeable mount not allowed

[1717713.408675] BTRFS warning (device dm-8): missing devices (1) exceeds the limit (0), writeable mount is not allowed [1717713.446453] BTRFS error (device dm-8): open_ctree failed [chris@f25s ~]$ uname -r 4.9.8-200.fc25.x86_64 I thought this was fixed. I'm still getting a one time degraded rw

Re: Please add more info to dmesg output on I/O error

On Wed, Mar 1, 2017 at 9:04 AM, Timofey Titovets wrote: > Hi, today i try move my FS from old HDD to new SSD > While processing i catch I/O error and device remove operation was canceled > > Dmesg: > [ 1015.010241] blk_update_request: I/O error, dev sda, sector 81353664 > [

Re: [PATCH 1/8] nowait aio: Introduce IOCB_FLAG_NOWAIT

On Wed, Mar 01, 2017 at 10:57:17AM -0600, Goldwyn Rodrigues wrote: > RWF_* ? Isn't that kernel space flags? Or did you intend to say > IOCB_FLAG_*? No, they are the flags for preadv2/pwritev2. > If yes, we maintain two flag fields? aio_reserved1 (perhaps > renamed to aio_flags2) and aio_flags?

Re: assertion failed: last_size == new_size, file: fs/btrfs/inode.c

On Tue, Feb 28, 2017 at 05:12:01PM -0800, Liu Bo wrote: > On Mon, Feb 27, 2017 at 11:23:42AM -0500, Dave Jones wrote: > > On Mon, Feb 27, 2017 at 07:53:48AM -0800, Liu Bo wrote: > > > On Sun, Feb 26, 2017 at 07:18:42PM -0500, Dave Jones wrote: > > > > Hitting this fairly frequently.. I'm not

Re: Please add more info to dmesg output on I/O error

Am Wed, 1 Mar 2017 19:04:26 +0300 schrieb Timofey Titovets : > Hi, today i try move my FS from old HDD to new SSD > While processing i catch I/O error and device remove operation was > canceled > > Dmesg: > [ 1015.010241] blk_update_request: I/O error, dev sda, sector

Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists

On Wednesday 01 March 2017 19:14:07 Marc Joliet wrote: > > > Also, the image is complete, so I only need to find somewhere where I > > > can > > > upload a 9.4 GB file. > > > > > > > > Is it a compressed dump? Dumped with btrfs-image -c9? > > It was created with: > > btrfs-image -s -w /dev/sdb2

Re: [PATCH] btrfs-progs: docs: fix many typos, plus three edits for clarit

On Tue, Feb 21, 2017 at 06:14:37PM -0500, Nicholas D Steeves wrote: > Hi David, > > Please see attached a reasonably thorough patch for all the typos I > could find in btrfs-progs documentation. The three edits are very > minor and look larger than they are because I had to reflow the >

Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists

On Wednesday 01 March 2017 19:14:07 Marc Joliet wrote: > > And btrfs check --mode=lowmem is also recommended as in some rare case, > > low mem mode can detect bug which original mode doesn't. > > I did see differences in output the last time around (again, see my > previous messages in this

Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists

On Wednesday 01 March 2017 17:32:35 Qu Wenruo wrote: > At 03/01/2017 04:23 PM, Marc Joliet wrote: > > On Tuesday 28 February 2017 23:14:54 Marc Joliet wrote: > >> I think I'm at that point now myself, unless anybody has any other ideas. > > > > For example, could the --init-extent-tree option to

Re: [PATCH 1/8] nowait aio: Introduce IOCB_FLAG_NOWAIT

On 03/01/2017 09:56 AM, Christoph Hellwig wrote: > On Wed, Mar 01, 2017 at 07:36:48AM -0800, Christoph Hellwig wrote: >> Given that we aren't validating aio_flags in older kernels we can't >> just add this flag as it will be a no-op in older kernels. I think >> we will have to add

Re: [PATCH v3 00/12] lowmem mode fixes

On Tue, Feb 21, 2017 at 04:34:26PM +0800, Qu Wenruo wrote: > Patches can be fetch from github: > https://github.com/adam900710/btrfs-progs/tree/lowmem_fixes > > Thanks for reports from Chris Murphy and Christoph Anton Mitterer, > several new bugs are exposed for lowmem mode fsck. > > Special

Re: [PATCH v3 10/12] btrfs-progs: fsck-test: Add new test case for file extent false alerts

On Tue, Feb 21, 2017 at 04:34:36PM +0800, Qu Wenruo wrote: > +check_global_prereq xfs_io > + run_check xfs_io -c "pwrite 0 64K" "$TEST_MNT/file" > + run_check xfs_io -f -c "pwrite 0 1K" "$TEST_MNT/file" I've converted this to dd as we don't want to depend on xfsprogs installed for the

Please add more info to dmesg output on I/O error

Hi, today i try move my FS from old HDD to new SSD While processing i catch I/O error and device remove operation was canceled Dmesg: [ 1015.010241] blk_update_request: I/O error, dev sda, sector 81353664 [ 1015.010246] BTRFS error (device sdb1): bdev /dev/sda1 errs: wr 0, rd 23, flush 0, corrupt

Re: [PATCH] btrfs-progs: send-dump: add missing newlines

On Wed, Feb 22, 2017 at 10:32:46PM +0100, Benedikt Morbach wrote: > make sure to include newlines after commands that have only one > argument, such as 'unlink' or 'mkfile' > > changes > > unlink ./baz.0/file_autimes ./baz.0/ >

Re: [PATCH 1/8] nowait aio: Introduce IOCB_FLAG_NOWAIT

On Wed, Mar 01, 2017 at 07:36:48AM -0800, Christoph Hellwig wrote: > Given that we aren't validating aio_flags in older kernels we can't > just add this flag as it will be a no-op in older kernels. I think > we will have to add IOCB_CMD_PREADV2/IOCB_CMD_WRITEV2 opcodes that > properly validate

Re: [PATCH v3] btrfs: remove btrfs_err_str function from uapi/linux/btrfs.h

On Wed, Mar 01, 2017 at 02:12:50AM +0300, Dmitry V. Levin wrote: > btrfs_err_str function is not called from anywhere and is replicated > in the userspace headers for btrfs-progs. > > It's removal also fixes the following linux/btrfs.h userspace > compilation error: > >

Re: [PATCH 7/8] nowait aio: xfs

> @@ -528,12 +528,17 @@ xfs_file_dio_aio_write( > ((iocb->ki_pos + count) & mp->m_blockmask)) { > unaligned_io = 1; > iolock = XFS_IOLOCK_EXCL; > + if (iocb->ki_flags & IOCB_NOWAIT) > + return -EAGAIN; So all unaligned I/O will

Re: [PATCH 3/8] nowait aio: return if direct write will trigger writeback

On Tue, Feb 28, 2017 at 07:46:06PM -0800, Matthew Wilcox wrote: > Ugh, this is pretty inefficient. If that's all you want to know, then > using the radix tree directly will be far more efficient than spinning > up all the pagevec machinery only to discard the pages found. > > But what's going to

Re: [PATCH 1/8] nowait aio: Introduce IOCB_FLAG_NOWAIT

On Tue, Feb 28, 2017 at 05:36:03PM -0600, Goldwyn Rodrigues wrote: > From: Goldwyn Rodrigues > > This flag informs kernel to bail out if an AIO request will block > for reasons such as file allocations, or a writeback triggered, > or would block while allocating requests while

Re: [PATCH 2/8] nowait aio: Return if cannot get hold of i_rwsem

Looks fine, Reviewed-by: Christoph Hellwig -- 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: [PULL] Btrfs cleanups for 4.11, part 2

On Wed, Mar 01, 2017 at 09:36:38AM +0200, Nikolay Borisov wrote: > Kbuild reported the following warning: > > fs/btrfs/scrub.c: In function 'check_extent_to_block': > >> fs/btrfs/scrub.c:4259:24: error: passing argument 1 of 'btrfs_get_extent' > >> from incompatible pointer type

Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists

At 03/01/2017 04:23 PM, Marc Joliet wrote: On Tuesday 28 February 2017 23:14:54 Marc Joliet wrote: I think I'm at that point now myself, unless anybody has any other ideas. For example, could the --init-extent-tree option to btrfs-check help, given that I needed to pass -w to btrfs-image?

Re: [PATCH 2/2] Btrfs: remove start_pos

At 03/01/2017 09:04 AM, Liu Bo wrote: @pos, not aligned @start_pos, should be used to check whether the eof page needs to be marked as readonly, thus @start_pos can be removed. Signed-off-by: Liu Bo --- fs/btrfs/file.c | 7 +-- 1 file changed, 1 insertion(+), 6

Re: [PULL] Btrfs cleanups for 4.11, part 2

On 1.03.2017 00:35, Chris Mason wrote: > > > On 02/28/2017 10:09 AM, David Sterba wrote: >> Hi, >> >> this is the second half of the 4.11 batch, the rest of the cleanups. >> Please >> pull, thanks. >> >> The following changes since commit >> 6288d6eabc7505f42dda34a2c2962f91914be3a4: >> >>

Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists

On Tuesday 28 February 2017 23:14:54 Marc Joliet wrote: > I think I'm at that point now myself, unless anybody has any other ideas. For example, could the --init-extent-tree option to btrfs-check help, given that I needed to pass -w to btrfs-image? Also, the image is complete, so I only need to