Re: misc/021-image-multi-devices fails on latest btrfs-devel/misc-next

2017-11-23 Thread Lakshmipathi.G
Hi Qu, I'm using btrfs-progs devel branch. mount command is failing with misc/021. When I tried to manually mount it. dmesg shows "unrecognized super flag: 17179869184" and interestingly "df -h" shows 16E as available! https://asciinema.org/a/4JGYg7YGQz1PHtdBRJ6AVw0fh Let me check further.

Re: [PATCH 1/3] btrfs: Introduce macros to handle bytes and sector conversion

2017-11-23 Thread Qu Wenruo
On 2017年11月24日 14:53, Nikolay Borisov wrote: > > > On 24.11.2017 06:10, Qu Wenruo wrote: >> Since block I/O is always done in unit of 512 bytes, add BI_SECTOR_SIZE >> and BI_SECTOR_SHIFT macros and to_sector() and to_bytes() for later >> use. >> >> Although the best position to define such

Re: [PATCH 1/3] btrfs: Introduce macros to handle bytes and sector conversion

2017-11-23 Thread Nikolay Borisov
On 24.11.2017 06:10, Qu Wenruo wrote: > Since block I/O is always done in unit of 512 bytes, add BI_SECTOR_SIZE > and BI_SECTOR_SHIFT macros and to_sector() and to_bytes() for later > use. > > Although the best position to define such things should be bvec.h, and > to_sector() to_bytes() are

[PATCH] btrfs-progs: mkfs: fix verbose value

2017-11-23 Thread Misono, Tomohiro
The value of 'verbose' is either 1 (default) or 0 (-q) and "verbose >= 2" will not be true. After fix this, we get something like: adding device /dev/sde id 2 adding device /dev/sdf id 3 during mkfs time when multiple devices are used. Signed-off-by: Tomohiro Misono

[PATCH] btrfs-progs: mkfs: check the status of file at mkfs

2017-11-23 Thread Misono, Tomohiro
Currently, only the status of block devices is checked at mkfs, but we should also check for regular files whether they are already formatted or mounted to prevent overwrite accidentally. Device status is checked by test_dev_for_mkfs(). The part which is not related to block device is split from

Re: misc/021-image-multi-devices fails on latest btrfs-devel/misc-next

2017-11-23 Thread Lakshmipathi.G
Hi Qu, I'm using the same instance. Let me check again with and without the commits list on Nov-23 (https://github.com/kdave/btrfs-devel/commits/misc-next) and get back with results. Cheers, Lakshmipathi.G http://www.giis.co.in http://www.webminal.org -- To unsubscribe from this list: send

[PATCH 1/3] btrfs: Introduce macros to handle bytes and sector conversion

2017-11-23 Thread Qu Wenruo
Since block I/O is always done in unit of 512 bytes, add BI_SECTOR_SIZE and BI_SECTOR_SHIFT macros and to_sector() and to_bytes() for later use. Although the best position to define such things should be bvec.h, and to_sector() to_bytes() are also defined in device-mapper.h, there are a lot of

[PATCH 3/3] btrfs: extent-tree: Use round up to replace align macro

2017-11-23 Thread Qu Wenruo
To save reader seconds before checking if it's rounding up or down. Signed-off-by: Qu Wenruo --- fs/btrfs/extent-tree.c | 10 +- fs/btrfs/extent_io.c| 8 fs/btrfs/file-item.c| 4 ++-- fs/btrfs/file.c | 6 +++--- fs/btrfs/inode-map.c| 4

[PATCH 2/3] btrfs: Cleanup open coded sector and bytes convert

2017-11-23 Thread Qu Wenruo
Signed-off-by: Qu Wenruo --- fs/btrfs/check-integrity.c | 2 +- fs/btrfs/compression.c | 7 --- fs/btrfs/extent-tree.c | 12 ++-- fs/btrfs/extent_io.c | 20 ++-- fs/btrfs/file-item.c | 6 +++--- fs/btrfs/inode.c | 16

Re: misc/021-image-multi-devices fails on latest btrfs-devel/misc-next

2017-11-23 Thread Qu Wenruo
On 2017年11月23日 11:16, Lakshmipathi.G wrote: > Quick update: It continues to fail: > https://asciinema.org/a/8HAL3uZ4MG7eb5gXnlgq3jm7q Still fails to reproduce it. All success across my host and VMs. And according to your misc-test-result, it seems that your testing system doesn't cleanup loop

Re: Issue in recovering and using the mirror superblock

2017-11-23 Thread Qu Wenruo
On 2017年11月24日 00:31, kol...@caramail.com wrote: > Hi, > > I am trying to recover from a mistake I made by overwriting the first GBs of > my Btrfs /home partition with a non-Btrfs filesystem. Well, in most case, the chance of recovery is already very low. The possibility mostly relies on

Re: notification about corrupt files from "btrfs scrub" in cron

2017-11-23 Thread Duncan
ST posted on Thu, 23 Nov 2017 13:47:59 +0200 as excerpted: >> > I have following cron job to scrub entire root filesystem (total ca. >> > 7.2TB and 2.3TB of them used) once a week: >> > /bin/btrfs scrub start -r / > /dev/null >> > >> > Such scrubbing takes ca. 2 hours. How should I get notified

python-btrfs release v9

2017-11-23 Thread Hans van Kranenburg
I just tagged v9 of the python btrfs library. https://github.com/knorrie/python-btrfs Q: What is python-btrfs? A: python-btrfs is a python3 implementation of the data structures for btrfs metadata, and an implementation of the kernel API (via ioctl calls) that btrfs provides to userland. Q: Ok,

Re: Issue in recovering and using the mirror superblock

2017-11-23 Thread koller
As an update to my previous email: I attempted the visual inspection of the second superblock (located at 256 GB) inside the .dd image by using tail -c +$((0x40+1)) /run/media/user01/SamsungHD/sda2.dd |hexdump -C|less and sure enough, it shows that the supeblock is right there,

Re: btrfs-progs-4.13: cmds-inspect-tree-stats.h: No such file or directory

2017-11-23 Thread David Sterba
On Wed, Nov 22, 2017 at 11:20:52PM -0500, John L. Center wrote: > On 11/22/2017 11:15 PM, John L. Center wrote: > > On 09/09/2017 01:48 AM, Uli Heller wrote: > >> I dowloaded the btrfs-progs-v4.13.tar.xz tarball and tried to build it. > >> Unfortunately, I get an error about

Re: [PATCH v2 00/11] Metadata specific accouting and dirty writeout

2017-11-23 Thread David Sterba
On Wed, Nov 22, 2017 at 04:15:55PM -0500, Josef Bacik wrote: > These patches are to support having metadata accounting and dirty handling > in a generic way. For dirty metadata ext4 and xfs currently are limited by > their journal size, which allows them to handle dirty metadata flushing in a >

Issue in recovering and using the mirror superblock

2017-11-23 Thread koller
Hi, I am trying to recover from a mistake I made by overwriting the first GBs of my Btrfs /home partition with a non-Btrfs filesystem. I have already made a .dd image of the partition, and I am using it to try and find the mirror superblock, in particular the one at 256 GB. When I run the

Re: uncorrectable errors in Raid 10

2017-11-23 Thread Steffen Sindzinski
Hi, I think just some XWayland Nouveau bug: Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: TRAP ch 22 [007d08d000 Xwayland[781]] Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 8041 Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: GPC0/TPC1/TEX:

Re: notification about corrupt files from "btrfs scrub" in cron

2017-11-23 Thread Marat Khalili
On 23/11/17 15:59, Mike Fleetwood wrote: Cron starts configured jobs at the scheduled time asynchronously. I.e. It doesn't block waiting for each command to finish. Cron notices when the job finishes and any output produced, written to stdout and/or stderr, by the job is emailed to the user.

Re: notification about corrupt files from "btrfs scrub" in cron

2017-11-23 Thread Mike Fleetwood
On 23 November 2017 at 11:47, ST wrote: > >> > I have following cron job to scrub entire root filesystem (total ca. >> > 7.2TB and 2.3TB of them used) once a week: >> > /bin/btrfs scrub start -r / > /dev/null >> > >> > Such scrubbing takes ca. 2 hours. How should I get notified

Re: uncorrectable errors in Raid 10

2017-11-23 Thread Qu Wenruo
On 2017年11月23日 20:02, Steffen Sindzinski wrote: > Hi, > > I updated to btrfs-progs v4.14-5-gf09e98a3. Unfortunately after 10h > Gnome desktop / Arch crashed with btrfs check --lowmem unfinished. I > will run it this night again. Any kernel backtrace about the crash? IIRC user space program

Re: uncorrectable errors in Raid 10

2017-11-23 Thread Steffen Sindzinski
Hi, I updated to btrfs-progs v4.14-5-gf09e98a3. Unfortunately after 10h Gnome desktop / Arch crashed with btrfs check --lowmem unfinished. I will run it this night again. The result until crash was: Checking filesystem on /dev/sdd2 UUID: 4fafd0d4-7dd9-4dcc-9a33-5f1ad9555358 ERROR:

Re: notification about corrupt files from "btrfs scrub" in cron

2017-11-23 Thread ST
> > I have following cron job to scrub entire root filesystem (total ca. > > 7.2TB and 2.3TB of them used) once a week: > > /bin/btrfs scrub start -r / > /dev/null > > > > Such scrubbing takes ca. 2 hours. How should I get notified that a > > corrupt file was discovered? Does this command return

Re: notification about corrupt files from "btrfs scrub" in cron

2017-11-23 Thread Duncan
ST posted on Wed, 22 Nov 2017 21:54:10 +0200 as excerpted: > Hello, > > I have following cron job to scrub entire root filesystem (total ca. > 7.2TB and 2.3TB of them used) once a week: > /bin/btrfs scrub start -r / > /dev/null > > Such scrubbing takes ca. 2 hours. How should I get notified

Re: btrfs restore corrupt file

2017-11-23 Thread Duncan
Jorge Bastos posted on Wed, 22 Nov 2017 19:18:59 + as excerpted: > Hello, > > While doing btrfs checksum testing I purposely corrupted a file and got > the expect I/O error when trying to copy it, I also tested btrfs restore > to see if I could recover a known corrupt file and it did copy it

Re: btrfs restore corrupt file

2017-11-23 Thread Jorge Bastos
Thanks for the replies. Good to know it's working as expected, and I'm glad restore permits restoring a corrupt file since this may be desirable in some cases, but agree with Chris that it would be nice to get a warning if corruption is found or suspected. Jorge On Thu, Nov 23, 2017 at 7:43 AM,

★ lintaowenxue --“2018世界复合材料展览及会议”将于“3月”在“法国巴黎”举行 (地右P1-L-Me)

2017-11-23 Thread linux-btrfs-owner
尊敬的 lintaowen...@163.com 企业领导/公司负责人/业界专家,您好:       新材料为21世纪三大共性关键技术之一,已成为全球经济迅速增长的源动力和提升核心竞争力的战略焦点。材料作为制造业的基础,特别是新材料研究和产业发展的水平与规模,已经成为衡量一个国家科技进步和综合实力的重要标志。在新材料发展与应用中,复合材料占有相当重要的地位,特别广泛的应用在汽车、交通、风能、航空、航天、兵器、船舶、国防、机械、电子、化工、建筑、农业、渔业、纺织、运动器材等领域,一直是世界各国优先发展和竞争激烈的重要行业。      “JEC世界复合材料展览及会议”(JEC world

[PATCH] btrfs: Remove redundant FLAG_VACANCY

2017-11-23 Thread Nikolay Borisov
Commit 9036c10208e1 ("Btrfs: update hole handling v2") added the FLAG_VACANCY to denote holes, however there was already a consistent way of flagging extents which represent hole - ->block_start = EXTENT_MAP_HOLE. And also the only place where this flag is checked is in the fiemap code, but the