-
-
Notifications
You must be signed in to change notification settings - Fork 41
Closed
Labels
bugSomething isn't workingSomething isn't workingfixplementedThis bug has already been fixed/this feature has already been implemented in a released versionThis bug has already been fixed/this feature has already been implemented in a released version
Milestone
Description
Hi,
Using Nextor 2.12, allocating a new 512 block to an existing open file seems to cause immediate crash.
It happens easily with akid, when editing a file an saving changes after adding enough text to pass the next 512 byte boundary in file length.
Steps to reproduce:
- Create a file in akid with close to 512 bytes, i.e. 510 bytes, then save it and check the file size
- Edit it again and add some more bytes to cross the boundary of 512 bytes
- Nextor hangs, some times even causing a reboot. File is modified but remains in previous size or truncated in the 512 byte boundary (no new blocks seem to have been allocated?)
- The test is done
in a fat16 partition<- fat12 seems to fail just the same - The file size boundary does not need to require a new cluster (it happens with in-cluster increase too)
(Example file included)
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingfixplementedThis bug has already been fixed/this feature has already been implemented in a released versionThis bug has already been fixed/this feature has already been implemented in a released version