From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [10.34.131.78] (dhcp131-78.brq.redhat.com [10.34.131.78]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tBEALoRm006978 for ; Mon, 14 Dec 2015 05:21:50 -0500 References: <02c701d13102$e0027c90$a00775b0$@helmholtz-muenchen.de> <000b01d1312a$8f8105c0$ae831140$@helmholtz-muenchen.de> From: Zdenek Kabelac Message-ID: <566E983E.3050901@redhat.com> Date: Mon, 14 Dec 2015 11:21:50 +0100 MIME-Version: 1.0 In-Reply-To: Content-Transfer-Encoding: 8bit Subject: Re: [linux-lvm] backup with snapshots - some principal questions Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="utf-8"; format="flowed" To: LVM general discussion and development Dne 9.12.2015 v 18:52 Stefan Ring napsal(a): > On Mon, Dec 7, 2015 at 9:05 PM, Lentes, Bernd > wrote: >> What does the message " ext3_orphan_cleanup: deleting unreferenced inode >> xxxxxx" means ? >> And it appears always when the script runs. > > I'm not entirely sure, but I would guess that these are deleted files > that were kept alive by some process holding them open at the time the > snapshot was taken. Since this unreferenced space would be leaked in > the event of a system crash – and snapshotting behaves essentially > like a crash –, the log recovery routine cleans them up during mount. Hi When lvm2 creates a volume snapshot - it does 2 things during needed suspend, it's using 'fsfreeze' and it's flushing all bio in process, so it's not comparable with just a plain crash. Zdenek