[PATCH v2] Btrfs: fix invalid page accesses in extent_same (dedup) ioctl

From: Filipe Manana In the extent_same ioctl we are getting the pages for the source and target ranges and unlocking them immediately after, which is incorrect because later we attempt to map them (with kmap_atomic) and access their contents at btrfs_cmp_data(). When we do

Re: "WARNING: device 0 not present" during scrub?

On 30 January 2016 at 21:10, Henk Slager wrote: > Can you mount the fs (readonly)? No idea, it's still mounted (rw even), aside from the scrub failing and debug-tree crashing I wouldn't know anything was amiss. I was kind of reluctant to shut the machine down lest it then

Re: "WARNING: device 0 not present" during scrub?

On Sat, Jan 30, 2016 at 12:59 PM, Christian Pernegger wrote: > Hello, > > tonight's scrub was cancelled after a "WARNING: device 0 not present". > No other visible errors or abnormalities. > > Google dragged up a linux-btrfs discussion from May 2015, but some of > it seems to

Re: RAID1 disk upgrade method

On Sat, Jan 30, 2016 at 7:50 AM, Patrik Lundquist wrote: > On 29 January 2016 at 13:14, Austin S. Hemmelgarn > wrote: >> >> Last I checked, Seagate's 'NAS' drives and whatever they've re-branded their >> other enterprise line as, as well as

Re: "WARNING: device 0 not present" during scrub?

On Sat, Jan 30, 2016 at 4:59 AM, Christian Pernegger wrote: > parent transid verify failed on 4693971959808 wanted 14495 found 14497 > parent transid verify failed on 4693971959808 wanted 14495 found 14497 > parent transid verify failed on 4693971959808 wanted 14495 found

Re: "WARNING: device 0 not present" during scrub?

On Sat, Jan 30, 2016 at 2:19 PM, Christian Pernegger wrote: > >> An an obvious advice is to use a 4.4 kernel and tools. Debian 'stable' >> doesn't mean >> that every piece of the kernel and tooling fits that 'stamp'. [...] Maybe >> you could switch >> to a rolling release