On Thu, 2012-08-09 at 09:40 +0200, root wrote: > Package: linux-image-3.2.0-3-amd64 > Version: 3.2.21-3 > Severity: normal > > Hello, > i'm using this virtual machine to export iscsi targets for windows machines to backup. > It has 620GB btrfs partition with 550GB iscsi file_io LUN exported. > I'm using btrfs snapshots to transport (consistent copy of) this big file to secondary backup storage (qnap and usb disk) - it takes around 12 hours to transport - thats reason to use snapshots. > Everything was working fine, until i run out of space on btrfs (because of snapshot and fullbackup from windows combination). > Since than, i have created fresh filesystem and create empty new file to export over iscsi. > Now, around 250GB of writen data do iscsi file, kern.log starts to fill with these messages > vfs_writev() returned -28 > > It keeps to show on every access to iscsi (even "rescan disk" operation in windows triggers it) Any read access may change the image file's access time (atime) if you don't use the 'noatime' mount option. On btrfs, metadata changes may allocate more disk space. > I was suspecting btrfs, but there is no oops in kern.log. > > I tried to google this error and found nothing relevant. Error 28 is ENOSPC: No space left on device. > I tried to reset everything (new filesystem, empty file, remove/add target from windows) and this errors comes back after writing approx. 250GB of data. > (Before problem, file was filled to around 540GB). > > Size now: > # du -cms iscsiSBS > 244561 iscsiSBS [...] What does 'btrfs filesystem df /btrfs' say (substitute the actual mountpoint for the btrfs volume)? Ben. -- Ben Hutchings Sturgeon's Law: Ninety percent of everything is crap.
Attachment:
signature.asc
Description: This is a digitally signed message part