Open GoogleCodeExporter opened 9 years ago
I would _definitely_ benefit from something like this, though IMHO I think it
should be separated from the s3fs binary a la the Unix philosophy, "Write
programs that do one thing and do it well." It's a good argument for splitting
s3 operations into a single library we could share between s3fs and "s3fs-util".
Just my 2¢
Original comment by ben.lema...@gmail.com
on 17 Feb 2011 at 9:15
I do agree (a separate utility). But like you said, things would need to be
split up to share the routines. I started down the refactoring path at one
point in time and it became a mess and I decided to spend my time on bug fixes
and improvements rather than unraveling the whole thing. (I think that Adrian
started down this path at one point in time as well).
Right now I have a bucket with debris from a multipart upload gone bad and am
in need of the abort function to clean up the debris -- that's why the idea of
this came up. If you have ever run the -u option, it may report the trash. BTW,
amazon still charges for storage space on unfinished, non-aborted multipart
uploads.
Original comment by dmoore4...@gmail.com
on 26 Feb 2011 at 6:51
Original issue reported on code.google.com by
dmoore4...@gmail.com
on 12 Feb 2011 at 4:05