Hi Shirish, On Sun, 16 Nov 2008, shirish wrote: > > Could you give a bit more insight about snapshotting. > > Please correct me if I am wrong . From what I understand of snapshots > its basically making a checkpoint at a specific point in time. In case > if any transaction or anything goes wrong after that it sorts of comes > back to the time when the snapshot was done. > > The down-side of having snapshots are :- > > a. It takes quite a bit of space to make snapshots > b. One has to remember to take snapshots from time to time to have it > current. (Of course one can have some sort of cron job or something so > it happens)
Think about it as automatic, micro-snapshotting, internal snapshotting, transparent snapshotting. By default it's off which means minimal snapshotting equivalent with journaling, if implemented accordingly. Historically file system development was sometimes quick hacks on hacks but by now some things become so complicated that they must be done "properly" and the different corner cases can give the hacks in the past. > > The top priority of the development will be always reliability and safe > > interoperability. Though we don't have much to do here at the moment, since > > we are not aware of any issues anymore. > > I do have an issue and will give more details in the bug-report a > little later. (or perhaps tomorrow with some more testing of the same) Please make sure it's not documented on http://ntfs-3g.org/support.html > >> and implementing the missing POSIX functionality. > > > > Well, to be honest, I don't know what we miss anymore. The Advanced NTFS-3G > > driver passes the PJD POSIX File System Test Suite without any fault: > > http://ntfs-3g.org/pjd-fstest.html > > bookmarking it for referencing later, perhaps change that bit on > wikipedia giving reference of the page. Good idea. > >> ntfs-3g itself doesn't have any documentation > > > > 'man ntfs-3g' and http://ntfs-3g.org > > Right, although what I mean is if you could have something in > /usr/share/doc as right now the only thing you have is a README in > there . > > If there could be a file which gives problem submission instructions > or for testing or something like that it would be nice . Just giving a > reference of ntfs-3g site is ok but it would be better to have > something more. The reason for the reference to the ntfs-3g site only is that, this way we can keep the document up-to-date. > Just the bit as given at http://www.ntfs-3g.org/support.html#bugreport > in a separate file would be nice. It would be nice to have an ntfs-3g.diag utility (shell script) which could diagnose and solve issues, or collect/report to us needed data for human debugging. Many users are not familiar with most relevant terms, processes, they don't want to learn and I think they shouldn't learn them. Regards, Szaka ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
