Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Files Files
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 423
    • Issues 423
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 71
    • Merge requests 71
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • FilesFiles
  • Merge requests
  • !1114

file-operations: Check before copy/move for 4GB limit on FAT

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Corey Berla requested to merge wip/corey/4gb into master Jan 23, 2023
  • Overview 12
  • Commits 3
  • Pipelines 2
  • Changes 1

Nautilus attempts to copy/move >4GB files to a FAT volume and fail once it reaches the 4GB threshold. The verify_destination() function already scans all of the source files before a copy / move, so we can add a 4GB check with almost no overhead. Add attributes to the SourceInfo to track the largest file. If that file exceeds 4GB, warn before initiating the operation. Similar to the existing before of copying to a volume with insufficient space, allow forcing the copy.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: wip/corey/4gb