Hi, Jelle de Jong wrote: > Dear Jean-Pierre, > > I could read the files for maybe one day, I tried to get it into > production but then it didn't work anymore, going back to my base test > mounting the volume without guestmount, so with just mount I get the > following:
Do you mean that the behavior with guestmount is different from the one guestmount ? Also, are you not able to read any file any more, or are there files which you can read (such as the one you could read previously) ? (more below) > # with stream list: > http://paste.debian.net/hidden/15d83c84/ > > root@backup:~# grep ntfs-3g /var/log/syslog > Feb 4 11:44:10 backup ntfs-3g[30845]: Version 2016.2.22AR.1 integrated > FUSE 28 > Feb 4 11:44:10 backup ntfs-3g[30845]: Mounted > /dev/mapper/lvm1--vol-sr7--disk2--snapshot--copy2 (Read-Only, label > "DATA", NTFS 3.1) > Feb 4 11:44:10 backup ntfs-3g[30845]: Cmdline options: ro > Feb 4 11:44:10 backup ntfs-3g[30845]: Mount options: > ro,allow_other,nonempty,relatime,fsname=/dev/mapper/lvm1--vol-sr7--disk2--snapshot--copy2,blkdev,blksize=4096 > > Feb 4 11:44:10 backup ntfs-3g[30845]: Ownership and permissions > disabled, configuration type 7 > Feb 4 11:47:10 backup ntfs-3g[30845]: Bad stream at offset 0x0 for file > 2801748 > Feb 4 11:47:10 backup ntfs-3g[30845]: Bad stream at offset 0x20000 for > file 2801748 > Feb 4 11:47:12 backup ntfs-3g[30845]: Bad stream at offset 0x0 for file > 2801748 > Feb 4 11:47:12 backup ntfs-3g[30845]: Bad stream at offset 0x20000 for > file 2801748 At first glance, this is related to the modification made a few weeks ago. Probably a wrong file was used, but I have no idea why. To debug this, I will need some data. To begin with, I need the reparse data of an unreadable file. You can get the reparse data by : (replace NAME by actual name) getfattr -h -e hex -n system.ntfs_reparse_data NAME I also need to know which one is the file 2801748. This should be in the directory which you have already listed (/mnt/sr7-sdb2/System*/ ... /Stream), just add -i to the "ls" options ("ls -hali /mnt/sr7-sdb2 ...") to display the inode numbers. > > I am at Fosdem 2017 this weekend, if you are there let me know. No, I am not. > Could you help me out and tell me what data you would like to have from me. I need to go through three steps, and analyze the data to get to the next step. The first step is the reparse data, as mentioned above. This is difficult to automate, as bugs tend to occur in unanticipated cases (I obviously have no specification, so I have no information about cases I never met myself). Note : please, only mount as read-only until the issue is solved. Regards Jean-Pierre > Kind regards, > > Jelle de Jong > > > On 18/01/17 21:52, Jean-Pierre André wrote: >> Hi again, >> >> Jelle de Jong wrote: >>> Dear Jean-Pierre, >>> >>> Thank you! I can read the files! >> >> Great ! >> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ ntfs-3g-devel mailing list ntfs-3g-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
