On 04/01/2021 23:36, Darrick J. Wong wrote:
> On Tue, Dec 22, 2020 at 12:48:55PM +0900, Naohiro Aota wrote:
>> A ZONE_APPEND bio must follow hardware restrictions (e.g. not exceeding
>> max_zone_append_sectors) not to be split. bio_iov_iter_get_pages builds
>> such restricted bio using __bio_iov_ap
On 12/01/2021 17:00, Josef Bacik wrote:
> You're completely ignoring errors here which isn't ok.
Fixed.
On Tue, Jan 12, 2021 at 02:24:09PM -0500, Josef Bacik wrote:
On 12/21/20 10:49 PM, Naohiro Aota wrote:
If more than one IO is issued for one file extent, these IO can be written
to separate regions on a device. Since we cannot map one file extent to
such a separate area, we need to follow the "o
On 12/1/21 10:41 pm, Josef Bacik wrote:
On 1/12/21 5:34 AM, Anand Jain wrote:
In the current kernel both scrub and balance fails due to ENOSPC,
however there is no reason that it should be transitioned to the
RDONLY and making free spaces difficult.
Signed-off-by: Anand Jain
---
fs/btrfs/sup
Caro Vеrdiеnеn Sie Gеld onlinе - 15446 EUR + pаssivеs Einkоmmеn
__
https://www.google.com/url?q=https%3A%2F%2Fvk.cc%2FbW9Ahb&sa=D&arq=lro&usg=AFQjCNE6WXsUPEp5dNV1lG_u3VDmHzsWHA
___
Desideriamo darvi il benvenuto a www.brianzarestart.it.
Con il tuo account, ora è possibile part
On Tue, Dec 22, 2020 at 12:49:01PM +0900, Naohiro Aota wrote:
> @@ -296,12 +383,22 @@ int btrfs_get_dev_zone_info(struct btrfs_device *device)
>
> device->zone_info = zone_info;
>
> - /* device->fs_info is not safe to use for printing messages */
> - btrfs_info_in_rcu(NULL,
NULL
On 13/01/2021 19:00, David Sterba wrote:
> so what changed that it's fine to use device->fs_info now while it was
> not before?
The time when we call btrfs_get_dev_zone_info() in "btrfs: defer loading
zone info after opening trees".
>From the commit message:
"The current call site of btrfs_get_
>
> Hi,
>
> I've 6x 3TB HDD RAID1 BTRFS filesystem where HBA card failed and
> caused some corruption.
> When I try to mount it I get
> $ mount /dev/sdt /mnt
> mount: /mnt/: wrong fs type, bad option, bad superblock on /dev/sdt,
> missing codepage or helper program, or other error
> $ dmesg | tail
Hi,
I've 6x 3TB HDD RAID1 BTRFS filesystem where HBA card failed and
caused some corruption.
When I try to mount it I get
$ mount /dev/sdt /mnt
mount: /mnt/: wrong fs type, bad option, bad superblock on /dev/sdt,
missing codepage or helper program, or other error
$ dmesg | tail -n 9
[ 617.158962]
Howdy,
I was looking through the mount options and being a madman with strong
opinions I can't help thinking that a lot of them does not really belong
as mount options at all, but should rather be properties set on the
subvolume - for example the toplevel subvolume.
And any options set on a
10 matches
Mail list logo
