tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

pyfilesystem tahoe-lafs mounted with fuse does not handles fs.errors.StorageSpaceError #1652

New issue
Open
opened 2012-01-07 08:31:39 +00:00 by vrusinov · 0 comments
vrusinov commented 2012-01-07 08:31:39 +00:00
Owner
Copy link

Linked issue: https://github.com/PyFilesystem/pyfilesystem/issues/101

Please, take a look to it. Pyfileystsem seems to be great way of using tahoe-lafs like regular filesystem, but currently there's no way to ensure that files you are writing to it are being saved.

What steps will reproduce the problem?

  1. Mount tahoe-lafs filesystem via fuse expose
  2. Copy lots of files, until there are not enough storage nodes accepting shares
  3. Next files are silently copied, producing 0-byte files on tahoe lafs instead of full ones. There is no indication of it on any tool.

Part of log file:

(Overwriting 59-byte djvu file with the new one):

(11174160) Opening file /documents/books/FL Studio 3rd Edition.djvu in mode r+
(11174160) Opening existing file /documents/books/FL Studio 3rd Edition.djvu for reading
(11174160) Opening file /documents/books/FL Studio 3rd Edition.djvu in mode w
(11174160) Reading meta for /documents/books/FL Studio 3rd Edition.djvu
(11174160) Creating empty file /documents/books/FL Studio 3rd Edition.djvu
(11174160) Uploading file /documents/books/FL Studio 3rd Edition.djvu
(11174160) Reading meta for /documents/books/FL Studio 3rd Edition.djvu
(11174160) Uploading file /documents/books/FL Studio 3rd Edition.djvu
(11174160) Reading meta for /documents/books/FL Studio 3rd Edition.djvu
(11174160) Listing directory (listdirinfo) /documents/books
(11174160) Path /documents/books/FL Studio 3rd Edition.djvu is directory: 0

Copy process finished with no errors. Directory listing shows full size. I've waited for some time and executed umount:

(11174160) Uploading file /documents/books/FL Studio 3rd Edition.djvu
Exception fs.errors.StorageSpaceError: StorageSpaceError() in <bound method _CacheInvalidatingFile.__del__ of <fs.remote._CacheInvalidatingFile object at 0xabd050>> ignored
(11174160) Uploading file /documents/books/FL Studio 3rd Edition.djvu

How can I ensure that all files are really written to tahoe before returning success to cp/mc/whatever?

Linked issue: <https://github.com/PyFilesystem/pyfilesystem/issues/101> Please, take a look to it. Pyfileystsem seems to be great way of using tahoe-lafs like regular filesystem, but currently there's no way to ensure that files you are writing to it are being saved. What steps will reproduce the problem? 1. Mount tahoe-lafs filesystem via fuse expose 2. Copy lots of files, until there are not enough storage nodes accepting shares 3. Next files are silently copied, producing 0-byte files on tahoe lafs instead of full ones. There is no indication of it on any tool. Part of log file: (Overwriting 59-byte djvu file with the new one): ``` (11174160) Opening file /documents/books/FL Studio 3rd Edition.djvu in mode r+ (11174160) Opening existing file /documents/books/FL Studio 3rd Edition.djvu for reading (11174160) Opening file /documents/books/FL Studio 3rd Edition.djvu in mode w (11174160) Reading meta for /documents/books/FL Studio 3rd Edition.djvu (11174160) Creating empty file /documents/books/FL Studio 3rd Edition.djvu (11174160) Uploading file /documents/books/FL Studio 3rd Edition.djvu (11174160) Reading meta for /documents/books/FL Studio 3rd Edition.djvu (11174160) Uploading file /documents/books/FL Studio 3rd Edition.djvu (11174160) Reading meta for /documents/books/FL Studio 3rd Edition.djvu (11174160) Listing directory (listdirinfo) /documents/books (11174160) Path /documents/books/FL Studio 3rd Edition.djvu is directory: 0 ``` Copy process finished with no errors. Directory listing shows full size. I've waited for some time and executed umount: ``` (11174160) Uploading file /documents/books/FL Studio 3rd Edition.djvu Exception fs.errors.StorageSpaceError: StorageSpaceError() in <bound method _CacheInvalidatingFile.__del__ of <fs.remote._CacheInvalidatingFile object at 0xabd050>> ignored (11174160) Uploading file /documents/books/FL Studio 3rd Edition.djvu ``` How can I ensure that all files are really written to tahoe before returning success to cp/mc/whatever?
tahoe-lafs added the
unknown
major
defect
n/a
 labels 2012-01-07 08:31:39 +00:00
tahoe-lafs added this to the undecided milestone 2012-01-07 08:31:39 +00:00
tahoe-lafs added
code-frontend
 and removed
unknown
 labels 2014-09-11 22:41:25 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No labels
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No milestone
undecided
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1652
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?