From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from plane.gmane.org ([80.91.229.3]:47774 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750737AbaETXKR (ORCPT ); Tue, 20 May 2014 19:10:17 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WmtAl-0004RY-2y for linux-btrfs@vger.kernel.org; Wed, 21 May 2014 01:10:15 +0200 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 May 2014 01:10:15 +0200 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 May 2014 01:10:15 +0200 To: linux-btrfs@vger.kernel.org From: Duncan <1i5t5.duncan@cox.net> Subject: Re: [PATCH] [btrfs] add volid to failed csum messages Date: Tue, 20 May 2014 23:10:02 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: Alexandre Oliva posted on Tue, 20 May 2014 12:37:07 -0300 as excerpted: > The failed csum messages generated by btrfs mention the inode number, > but on filesystems with multiple subvolumes, that's not enough to > identify the file. I've added the inode number to the messages ?? s/added the inode number/added the volid/ ?? -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman